spec_coding_goal_confirmed

THE RISK

Medium Risk

Why spec_coding_goal_confirmed needs a policy

This tool writes workflow metadata (feature_name) and updates the state machine of a spec-driven development process. It does not execute arbitrary code or delete data, but it does create/modify structured data that affects downstream workflow execution.

From the tool's definition Tool name contains 'confirmed' and description states it sets the 'feature_name' and proceeds to the next workflow phase, indicating it creates or modifies workflow state and configuration data.

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

POLICY

How to control spec_coding_goal_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_goal_confirmed:

policy.json

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

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

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.

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_tasks_confirmed Confirm the completion of task planning and proceed to the execution phase 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 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about spec_coding_goal_confirmed

What does the spec_coding_goal_confirmed tool do? +

Confirm the completion of the feature goal, set the feature_name, and proceed to the requirements collection phase. It is categorised as a Write tool in the Spec-driven Development MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on spec_coding_goal_confirmed? +

Register the Spec-driven Development MCP Server MCP server in PolicyLayer and add a rule for spec_coding_goal_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_goal_confirmed? +

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

Can I rate-limit spec_coding_goal_confirmed? +

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

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

spec_coding_goal_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 →