record_criterion_progress · Planning System MCP Server MCP

WHAT IT DOES

What record_criterion_progress does on Planning System MCP Server

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

WHY IT NEEDS A POLICY

Why record_criterion_progress needs a policy

An AI agent can call record_criterion_progress faster than any human can review — one bad instruction and it creates or modifies resources in Planning System MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_criterion_progress Rate-limited

record_criterion_progress 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": {
    "record_criterion_progress": {
      "limits": [
        {
          "counter": "record_criterion_progress_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 Planning System MCP Server, so you can run agents against it safely.

FAQ

Questions about record_criterion_progress

What does the record_criterion_progress tool do? +

Record the latest observed value of one of a goal. It is categorised as a Write tool in the Planning System MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_criterion_progress? +

Register the Planning System MCP Server MCP server in PolicyLayer and add a rule for record_criterion_progress: 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 Planning System MCP Server. Nothing to install.

What risk level is record_criterion_progress? +

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

Can I rate-limit record_criterion_progress? +

Yes. Add a rate_limit block to the record_criterion_progress 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 record_criterion_progress completely? +

Set action: deny in the PolicyLayer policy for record_criterion_progress. 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 record_criterion_progress? +

record_criterion_progress is provided by the Planning System MCP Server MCP server (tagents/agent-planner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.