execute_task · MCP Shrimp Task Manager MCP: Risk & Policy

WHAT IT DOES

What execute_task does on MCP Shrimp Task Manager

AI agents invoke execute_task to trigger actions in MCP Shrimp Task Manager. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_task needs a policy

The tool's primary function is to execute tasks, which aligns with the Execute category definition: 'runs code, shell commands, browser actions, or triggers external operations whose effects depend on arguments.' While not inherently Destructive (no explicit delete/drop operations mentioned), the ability to execute arbitrary programming tasks without visible guardrails represents a high-severity risk if misused by…

From the tool's definition Tool name 'execute_task' combined with description 'Execute a specific task with AI guidance' directly indicates execution of code or operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_task Rate-limited

execute_task stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_task": {
      "limits": [
        {
          "counter": "execute_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 execute_task

What does the execute_task tool do? +

Execute a specific task with AI guidance. It is categorised as a Execute tool in the MCP Shrimp Task Manager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_task? +

Register the MCP Shrimp Task Manager MCP server in PolicyLayer and add a rule for execute_task: 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 execute_task? +

execute_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_task? +

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

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

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