planning_update · Codecks MCP: Risk & Policy

WHAT IT DOES

What planning_update does on Codecks

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

WHY IT NEEDS A POLICY

Why planning_update needs a policy

This tool modifies planning documents and project records without explicit destructive operations (no delete/drop mentioned). While the specific file-level modifications could potentially overwrite existing content, the intent appears to be systematic updates to planning state rather than irreversible deletion.

From the tool's definition The tool name 'planning_update' combined with description 'Update planning files mechanically' indicates creation or modification of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

planning_update Rate-limited

planning_update 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": {
    "planning_update": {
      "limits": [
        {
          "counter": "planning_update_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 Codecks, so you can run agents against it safely.

FAQ

Questions about planning_update

What does the planning_update tool do? +

Update planning files mechanically. No auth needed. Operations: goal, advance, phase_status, error, decision, finding, issue, log, file_changed, test. It is categorised as a Write tool in the Codecks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on planning_update? +

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

What risk level is planning_update? +

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

Can I rate-limit planning_update? +

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

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

planning_update is provided by the Codecks MCP server (rangogamedev/codecks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.