AI agents use create_plan to create or update resources in Melo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Melo environment.
This tool creates a new plan object with up to 20 steps, which is a reversible creation operation. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), involves no financial transactions (ruling out Financial), and is more than a simple read operation. The ability to subsequently modify steps via update_plan_step suggests the plan is a modifiable data structure.
From the tool's definition Tool name 'create_plan' and description 'Create a Planning Mode plan' with mention of returning a planId for subsequent operations indicate creation of a new data structure/plan object.
Attacks that exploit this kind of access
Create a Planning Mode plan with up to 20 steps. Returns a planId you reference from update_plan_step and snapshot_checkpoint. Steps default to verifyWith=. It is categorised as a Write tool in the Melo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Melo 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 Melo. 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 Melo MCP server (yannyhl/linkedsword-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 →