task-executor · Spec MCP Server MCP: Risk & Policy

WHAT IT DOES

What task-executor does on Spec MCP Server

AI agents invoke task-executor to trigger actions in Spec MCP Server. 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 task-executor needs a policy

The tool executes tasks from a task list, providing implementation guidance and code patterns. While it may primarily guide rather than directly run code, 'executes' and 'implementing' strongly suggest it triggers automated implementation actions.

From the tool's definition 'Executes a specific task from tasks.md by providing detailed implementation guidance' and 'implementing one task thoroughly'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task-executor Rate-limited

task-executor 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": {
    "task-executor": {
      "limits": [
        {
          "counter": "task-executor_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 Spec MCP Server, so you can run agents against it safely.

FAQ

Questions about task-executor

What does the task-executor tool do? +

Executes a specific task from tasks.md by providing detailed implementation guidance, requirements, acceptance criteria, and code patterns. This tool focuses on implementing one task thoroughly. It is categorised as a Execute tool in the Spec MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on task-executor? +

Register the Spec MCP Server MCP server in PolicyLayer and add a rule for task-executor: 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 Spec MCP Server. Nothing to install.

What risk level is task-executor? +

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

Can I rate-limit task-executor? +

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

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

task-executor is provided by the Spec MCP Server MCP server (karol-f/spec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.