Policy Simulated 4 MCP tools

Policy Engine

Browse .ags/*.yml policies and watch enforcement animate.

How you use it

Keep the policy registry as the TOC of what must exist. After enabling an engine, policy_plan → add files → policy_enforce.

Token savings

Agents do not rediscover missing config through trial-and-error tool failures across a long session.

Consistency

Enabled engines always have their declared config files present and valid.

In action

Policy

Registry

policy_get loads .ags/policy.yml.

Bind

Gap

Enforce

Interactive demo

Enforcement Idle

# .ags/policy.yml (simulated)
version: 1
commit:
  require_enforcement: true
  allowed_status:
    - checkpoint
    - awaiting-user
staging:
  single_category: true
confidence:
  min_score: 0.72
blocks:
  - raw_git_commit
  - skip_hooks

Live evaluation

Agent action: git commit -m "fix"

Simulated behavior only — does not execute proprietary AGS engine code.

Diagram

Example usage

# .ags/policy.yml (conceptual)
engines:
  staging:
    requiredFiles: [.ags/staging.yml]
  sentinel:
    requiredFiles: [.ags/sentinel.yml]

# MCP: policy_enforce
{}

Docs →

policy_get
policy_validate
policy_enforce
policy_plan