Create a new development plan with phases and proposed tasks
AI agents use create_plan 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 new data (development plans) reversibly. It modifies application state by adding planning records, which is a Write category action. Severity is medium because misuse could create excessive or erroneous plans, but the impact is limited to planning artifacts that can be corrected or deleted without cascading damage to production systems.
From the tool's definition Tool name 'create_plan' and description 'Create a new development plan with phases and proposed tasks' indicate data creation functionality.
Attacks that exploit this kind of access
Create a new development plan with phases and proposed tasks. 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 create_plan: 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.
create_plan 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 create_plan 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 create_plan. 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.
create_plan 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 →