// SCAN REPORT

Mcp Taskmanager

10 tools. 7 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

7 can modify or destroy data

3 read-only

10 tools total

Community server · catalogue entry verified 11/06/2026

How to control Mcp Taskmanager ↓

TOOL MAP

What Mcp Taskmanager exposes to your agents

Read (3) Write / Execute (6) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mcp Taskmanager tools

Destructive · High delete_task This tool permanently removes tasks from the task management system. Write · Medium approve_request_completion The tool creates or modifies data (marking a request as finalized/completed) in a reversible manner. Write · Medium add_tasks_to_request This tool creates or modifies data (tasks) within an existing request structure in a reversible manner. Write · Medium approve_task_completion Approving task completion is a state-change operation that modifies the task's status in the queue system.

7 of Mcp Taskmanager's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mcp Taskmanager

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Taskmanager, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_task": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_tasks_to_request": {
    "limits": [
      {
        "counter": "add_tasks_to_request_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_next_task": {
    "limits": [
      {
        "counter": "get_next_task_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Mcp Taskmanager — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP TASKMANAGER →

Free to start. No card required.

FULL CATALOGUE

All 10 Mcp Taskmanager tools

DESTRUCTIVE 1 tools

Destructive delete_task Delete a specific task from a request. Only uncompleted tasks can be deleted.\n\n

WRITE 6 tools

Write add_tasks_to_request Add new tasks to an existing request. This allows extending a request with additional tasks.\n\n Write approve_request_completion After all tasks are done and approved, this tool finalizes the entire request. The user must call this to conf Write approve_task_completion Once the assistant has marked a task as done using Write mark_task_done Mark a given task as done after you Write request_planning Register a new user request and plan its associated tasks. You must provide Write update_task Update an existing task

READ 3 tools

Read get_next_task Given a Read list_requests List all requests with their basic information and summary of tasks. This provides a quick overview of all req Read open_task_details Get details of a specific task by

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Mcp Taskmanager

Can an AI agent delete data through the Mcp Taskmanager MCP server? +

Yes. The Mcp Taskmanager server exposes 1 destructive tools including delete_task. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Mcp Taskmanager? +

The Mcp Taskmanager server has 6 write tools including add_tasks_to_request, approve_request_completion, approve_task_completion. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mcp Taskmanager.

How many tools does the Mcp Taskmanager MCP server expose? +

10 tools across 3 categories: Destructive, Read, Write. 3 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Mcp Taskmanager? +

Register the Mcp Taskmanager MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Mcp Taskmanager tool call.

Deterministic rules across all 10 Mcp Taskmanager tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP TASKMANAGER →

Free to start. No card required.

10 Mcp Taskmanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.