create_task_plan

A other tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/create-task-plan.md

WHAT IT DOES

What create_task_plan does on Allcanuse

AI agents call create_task_plan as a supporting operation in Allcanuse workflows.

RISK

Why create_task_plan is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_task_plan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_task_plan, this is the rule to start with:

create_task_plan Rate-limited

create_task_plan gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_task_plan": {
      "limits": [
        {
          "counter": "create_task_plan_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every create_task_plan call is checked against it from then on.

FAQ

Questions about create_task_plan

What does the create_task_plan tool do? +

create_task_plan is a other tool on the Allcanuse MCP server. It is categorised as a Other tool in the Allcanuse MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on create_task_plan? +

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.

What risk level is create_task_plan? +

create_task_plan is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit create_task_plan? +

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.

How do I block create_task_plan completely? +

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.

What MCP server provides create_task_plan? +

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.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools →

Across the catalogue

my_task on Agent Jail → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →