Start the task planning phase and provide guidance for creating the task list
AI agents call spec_coding_tasks_start to retrieve information from Spec-driven Development MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool initiates a planning phase and provides guidance — it reads/retrieves workflow state and returns instructional content. It does not create, modify, execute, or delete data. The 'start' in the name suggests initiating a phase, but the description indicates it provides guidance rather than performing any write or execute actions.
From the tool's definition Start the task planning phase and provide guidance for creating the task list
Documented attack patterns abuse exactly the kind of access spec_coding_tasks_start gives an agent:
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_start:
{
"version": "1",
"default": "deny",
"tools": {
"spec_coding_tasks_start": {}
}
} spec_coding_tasks_start is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Start the task planning phase and provide guidance for creating the task list. It is categorised as a Read tool in the Spec-driven Development MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spec-driven Development MCP Server MCP server in PolicyLayer and add a rule for spec_coding_tasks_start: 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.
spec_coding_tasks_start is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spec_coding_tasks_start 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.
Set action: deny in the PolicyLayer policy for spec_coding_tasks_start. 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.
spec_coding_tasks_start 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.
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.
Free to start. No card required.
9 Spec-driven Development MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.