Generate a detailed implementation plan for a software development task. This tool enters Planning Mode, where it: 1. Analyzes the codebase context relevant to your task 2. Generates a structured, actionable implementation plan 3. Identifies dependencies, risks, and parallelization opportunities ...
AI agents use create_plan to create or update resources in Context Engine MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Context Engine MCP Server environment.
This tool creates and persists a structured implementation plan (a new artifact/document) in the system. It writes/stores the plan for later use by tools like execute_plan, complete_step, compare_plan_versions, and delete_plan. It doesn't execute code or destructively modify data — it generates and stores a reversible planning artifact, making Write the appropriate category.
From the tool's definition Generate a detailed implementation plan for a software development task... Creates architecture diagrams when explicitly requested
Documented attack patterns abuse exactly the kind of access create_plan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Context Engine MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_plan:
{
"version": "1",
"default": "deny",
"tools": {
"create_plan": {
"limits": [
{
"counter": "create_plan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_plan 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.
Free to start. No card required.
Generate a detailed implementation plan for a software development task. This tool enters Planning Mode, where it: 1. Analyzes the codebase context relevant to your task 2. Generates a structured, actionable implementation plan 3. Identifies dependencies, risks, and parallelization opportunities 4. Creates architecture diagrams when explicitly requested When to use this tool: - Before starting a complex feature or refactoring task - When you need to understand the scope and approach - To identify potential risks and dependencies upfront - When coordinating work that touches multiple files What you get: - Clear goal with scope boundaries - MVP vs nice-to-have feature breakdown - Step-by-step implementation guide - Dependency graph showing what can run in parallel - Risk assessment with mitigations - Testing strategy recommendations - Confidence score and clarifying questions The plan output includes both a human-readable summary and full JSON for programmatic use. By default, plans are persisted so they can be executed later via plan_id. It is categorised as a Write tool in the Context Engine MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Context Engine MCP Server 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 Context Engine MCP Server. 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 Context Engine MCP Server MCP server (kirachon/context-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Context Engine MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Context Engine MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.