spec_coding_tasks_confirmed

THE RISK

High Risk

Why spec_coding_tasks_confirmed needs a policy

This tool transitions the workflow to the code execution phase. While the tool itself appears to be a confirmation/state-transition action, it enables the triggering of code execution operations ('spec_coding_execute_start') based on its position in the documented workflow pipeline. The actual code execution would occur next, making this tool a critical control point.

From the tool's definition Tool description states it 'proceed to the execution phase' after task planning confirmation. The server description explicitly mentions 'systematic code execution' as a final stage, and this tool serves as the gateway to that execution phase.

Documented attack patterns abuse exactly the kind of access spec_coding_tasks_confirmed gives an agent:

POLICY

How to control spec_coding_tasks_confirmed

PolicyLayer is an MCP gateway — it sits between your AI agents and Spec-driven Development MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for spec_coding_tasks_confirmed:

policy.json

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

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

Create a free account and register Spec-driven Development MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Spec-driven Development MCP Server tools

Execute spec_coding_execute_start Start the task execution phase and provide guidance for task execution Execute spec_coding_workflow_start Start the specs workflow and begin the goal collection phase Write spec_coding_design_confirmed Confirm the completion of the design document and proceed to the task planning phase Write spec_coding_requirements_confirmed Confirm the completion of requirements collection and proceed to the design phase Write spec_coding_goal_confirmed Confirm the completion of the feature goal, set the feature_name, and proceed to the requi Read spec_coding_design_start Start the design documentation phase and provide guidance for creating design documents Read spec_coding_requirements_start Start the requirements collection phase and provide guidance for requirements gathering Read spec_coding_tasks_start Start the task planning phase and provide guidance for creating the task list

All 9 Spec-driven Development MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Spec-driven Development MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about spec_coding_tasks_confirmed

What does the spec_coding_tasks_confirmed tool do? +

Confirm the completion of task planning and proceed to the execution phase. It is categorised as a Execute tool in the Spec-driven Development 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 spec_coding_tasks_confirmed? +

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

What risk level is spec_coding_tasks_confirmed? +

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

Can I rate-limit spec_coding_tasks_confirmed? +

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

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

spec_coding_tasks_confirmed is provided by the Spec-driven Development MCP Server MCP server (kevinlin/spec-coding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Spec-driven Development MCP Server tool call.

Start from Spec-driven Development MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →