Generates and writes SPECIFICATION.md with all requirements in EARS notation. Validates each requirement against EARS patterns.
AI agents use sdd_write_spec to create or update resources in Specky — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Specky environment.
The tool creates and writes specification files (SPECIFICATION.md) containing requirements, which is a reversible modification of project artifacts. While it modifies important documentation, it does not execute code, delete data irreversibly, or commit financial transactions.
From the tool's definition Tool description states it 'Generates and writes SPECIFICATION.md' — a create/modify operation that produces structured specification documents.
Documented attack patterns abuse exactly the kind of access sdd_write_spec gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Specky, and nothing reaches the server without passing your rules. This is the rule we recommend for sdd_write_spec:
{
"version": "1",
"default": "deny",
"tools": {
"sdd_write_spec": {
"limits": [
{
"counter": "sdd_write_spec_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sdd_write_spec 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.
Free to start. No card required.
Generates and writes SPECIFICATION.md with all requirements in EARS notation. Validates each requirement against EARS patterns. It is categorised as a Write tool in the Specky MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Specky MCP server in PolicyLayer and add a rule for sdd_write_spec: 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 Specky. Nothing to install.
sdd_write_spec 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 sdd_write_spec 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 sdd_write_spec. 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.
sdd_write_spec is provided by the Specky MCP server (paulasilvatech/specky). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Specky, 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.
56 Specky tools catalogued and risk-classified — across an index of 43,000+ MCP servers.