Generate tasks.md (implementation plan & task breakdown) from your request and codebase. Writes
AI agents use generate-tasks to create or update resources in Spec MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spec MCP Server environment.
Tool creates/modifies a tasks.md file based on user request and codebase analysis. This is a reversible write operation—files can be edited or deleted. It does not execute code, delete irreversibly, move money, or trigger external operations. The 'Write' category applies because the tool generates and persists data (task breakdown/implementation plan).
From the tool's definition 'Writes' per description; generates and creates a tasks.md file as part of implementation planning workflow
Attacks that exploit this kind of access
Generate tasks.md (implementation plan & task breakdown) from your request and codebase. Writes. It is categorised as a Write tool in the Spec MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spec MCP Server MCP server in PolicyLayer and add a rule for generate-tasks: 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.
generate-tasks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate-tasks 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 generate-tasks. 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.
generate-tasks 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →