generate_plan
AI agents use generate_plan to create or update resources in Keshro MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keshro MCP environment.
The tool name suggests it creates or generates a plan, which aligns with the Write category (creating data). Sibling tools like 'create_plan' and 'edit_task' are Write operations. Since the description is empty, confidence is reduced, but based on naming conventions and context, this likely creates a new plan artifact. Severity is medium as a misused plan could misdirect an AI agent's engineering workflow.
From the tool's definition Tool name 'generate_plan' on a server that manages plans, tasks, and integrations. Description is empty, so classification relies on name and sibling context.
Attacks that exploit this kind of access
generate_plan. It is categorised as a Write tool in the Keshro MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keshro MCP server in PolicyLayer and add a rule for generate_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 Keshro MCP. Nothing to install.
generate_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 generate_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 generate_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.
generate_plan is provided by the Keshro MCP server (jlewitt1/keshro-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 →