AI agents use create_workplan to create or update resources in Yellhorn MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yellhorn MCP environment.
Based on the tool name alone, 'create_workplan' most likely generates or writes a new work plan document or record. In the context of this MCP server (which generates implementation plans and provides feedback on code changes), this tool likely creates a new workplan artifact.
From the tool's definition Tool name 'create_workplan' suggests creating a new artifact; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access create_workplan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yellhorn MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_workplan:
{
"version": "1",
"default": "deny",
"tools": {
"create_workplan": {
"limits": [
{
"counter": "create_workplan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_workplan 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.
create_workplan. It is categorised as a Write tool in the Yellhorn MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yellhorn MCP server in PolicyLayer and add a rule for create_workplan: 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 Yellhorn MCP. Nothing to install.
create_workplan 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_workplan 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_workplan. 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_workplan is provided by the Yellhorn MCP server (msnidal/yellhorn-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Yellhorn MCP, 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.
5 Yellhorn MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.