Update a plan proposal (title, description, status, tags, planIds)
AI agents use update_plan_proposal to create or update resources in Planning Game — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Planning Game environment.
This tool creates or modifies data (plan proposal metadata) in a reversible manner without deleting or destroying information. It falls clearly into the Write category rather than Read (it modifies, not retrieves), Execute (it updates structured data, not arbitrary code/operations), or Destructive (changes are reversible via subsequent updates).
From the tool's definition Tool description states 'Update a plan proposal' with modifiable fields (title, description, status, tags, planIds). The action is a reversible modification of existing data.
Attacks that exploit this kind of access
Update a plan proposal (title, description, status, tags, planIds). It is categorised as a Write tool in the Planning Game MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Planning Game MCP server in PolicyLayer and add a rule for update_plan_proposal: 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 Game. Nothing to install.
update_plan_proposal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_plan_proposal 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.
Set action: deny in the PolicyLayer policy for update_plan_proposal. 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.
update_plan_proposal is provided by the Planning Game MCP server (planning-game-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →