code_for_plan
AI agents invoke code_for_plan to trigger actions in AI Pull Request Generator. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the server context, this tool likely generates and possibly executes or writes code as part of the automated PR workflow. The name suggests it produces code for a given plan, which would be at minimum a Write operation (generating code artifacts), potentially Execute if it runs or applies the code. Given sibling tools handle planning and PR creation separately, this tool most likely generates/writes code.
From the tool's definition Tool name 'code_for_plan' combined with server description: 'automates the process of planning tasks, generating code, and creating GitHub pull requests.' No explicit description provided for the tool itself.
Attacks that exploit this kind of access
code_for_plan. It is categorised as a Execute tool in the AI Pull Request Generator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AI Pull Request Generator MCP server in PolicyLayer and add a rule for code_for_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 AI Pull Request Generator. Nothing to install.
code_for_plan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the code_for_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 code_for_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.
code_for_plan is provided by the AI Pull Request Generator MCP server (shougakusei/plan_pr_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 →