claim_directive · AT MCP: Risk & Policy

WHAT IT DOES

What claim_directive does on ATMcp

AI agents use claim_directive to create or update resources in ATMcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ATMcp environment.

WHY IT NEEDS A POLICY

Why claim_directive needs a policy

This tool modifies the status of a directive (from some pending state to 'running'). It is a reversible state update/write operation — it doesn't delete data, execute code, or involve finances. Misuse could cause coordination issues in multi-agent workflows (e.g., incorrectly claiming a directive), hence medium severity.

From the tool's definition Mark a directive addressed to you as 'running' before you start executing it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

claim_directive Rate-limited

claim_directive stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "claim_directive": {
      "limits": [
        {
          "counter": "claim_directive_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ATMcp, so you can run agents against it safely.

FAQ

Questions about claim_directive

What does the claim_directive tool do? +

Mark a directive addressed to you as 'running' before you start executing it. It is categorised as a Write tool in the ATMcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on claim_directive? +

Register the AT MCP server in PolicyLayer and add a rule for claim_directive: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ATMcp. Nothing to install.

What risk level is claim_directive? +

claim_directive is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit claim_directive? +

Yes. Add a rate_limit block to the claim_directive rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block claim_directive completely? +

Set action: deny in the PolicyLayer policy for claim_directive. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides claim_directive? +

claim_directive is provided by the AT MCP server (midcheck/atmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.