split_tasks · MCP Shrimp Task Manager MCP: Risk & Policy

WHAT IT DOES

What split_tasks does on MCP Shrimp Task Manager

AI agents use split_tasks to create or update resources in MCP Shrimp Task Manager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Shrimp Task Manager environment.

WHY IT NEEDS A POLICY

Why split_tasks needs a policy

This tool creates new subtask records by decomposing an existing task. It creates/modifies data in the task management system (adding subtasks), which is reversible (tasks can be deleted). No code execution, deletion, or financial operations are involved.

From the tool's definition Split complex tasks into manageable subtasks

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

split_tasks Rate-limited

split_tasks 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "split_tasks": {
      "limits": [
        {
          "counter": "split_tasks_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Shrimp Task Manager, so you can run agents against it safely.

FAQ

Questions about split_tasks

What does the split_tasks tool do? +

Split complex tasks into manageable subtasks. It is categorised as a Write tool in the MCP Shrimp Task Manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on split_tasks? +

Register the MCP Shrimp Task Manager MCP server in PolicyLayer and add a rule for split_tasks: 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 MCP Shrimp Task Manager. Nothing to install.

What risk level is split_tasks? +

split_tasks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit split_tasks? +

Yes. Add a rate_limit block to the split_tasks 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 split_tasks completely? +

Set action: deny in the PolicyLayer policy for split_tasks. 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 split_tasks? +

split_tasks is provided by the MCP Shrimp Task Manager MCP server (samihalawa/gist-task-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.