AI agents call create_task_plan as a supporting operation in Allcanuse workflows.
The description is empty, so classification is based solely on the name. 'create_task_plan' suggests creating a plan or schedule, which could be a Write operation. However, given the sibling tools (append_task_event, create_background_task, cancel_background_task) suggest a task management system, this likely creates a task plan/schedule (Write). Confidence is low due to empty description.
From the tool's definition Tool name is 'create_task_plan' and description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access create_task_plan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for create_task_plan:
{
"version": "1",
"default": "deny",
"tools": {
"create_task_plan": {
"limits": [
{
"counter": "create_task_plan_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}create_task_plan gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_task_plan. It is categorised as a Other tool in the Allcanuse MCP Server, which means it performs auxiliary operations.
Register the Allcanuse MCP server in PolicyLayer and add a rule for create_task_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 Allcanuse. Nothing to install.
create_task_plan is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the create_task_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_task_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_task_plan is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Allcanuse, 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.
130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.