AI agents use create_plan to create or update resources in Valkey MCP Task Management Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Valkey MCP Task Management Server environment.
This tool creates new plans in the Valkey persistence layer, which is a reversible write operation. It modifies the data store by adding a new record. While sibling tools include destructive operations (delete_plan, delete_task), this specific tool only creates data.
From the tool's definition Tool name is 'create_plan' and description states 'Create a new plan'. The server supports 'plan and task management' with 'create' being explicitly listed as a capability. This is a data creation operation.
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 Valkey MCP Task Management 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.
Create a new plan. It is categorised as a Write tool in the Valkey MCP Task Management Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Valkey MCP Task Management 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 Valkey MCP Task Management 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 Valkey MCP Task Management Server MCP server (jbrinkman/valkey-ai-tasks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Valkey MCP Task Management 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.
17 Valkey MCP Task Management Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.