Detects the project tech stack and generates a Docker-based local development environment (Dockerfile + docker-compose.yml). Returns a payload with routing_instructions for Docker MCP to create and manage containers.
AI agents invoke sdd_setup_local_env to trigger actions in Specky. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers external operations by detecting the tech stack, generating Docker configuration files, and routing instructions to Docker MCP to create and manage containers. It executes infrastructure setup with side effects that depend on the project context, classifying it as Execute. Severity is high because misuse could spin up unintended containers or expose services.
From the tool's definition generates a Docker-based local development environment (Dockerfile + docker-compose.yml). Returns a payload with routing_instructions for Docker MCP to create and manage containers
Documented attack patterns abuse exactly the kind of access sdd_setup_local_env 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_setup_local_env:
{
"version": "1",
"default": "deny",
"tools": {
"sdd_setup_local_env": {
"limits": [
{
"counter": "sdd_setup_local_env_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}sdd_setup_local_env 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.
Free to start. No card required.
Detects the project tech stack and generates a Docker-based local development environment (Dockerfile + docker-compose.yml). Returns a payload with routing_instructions for Docker MCP to create and manage containers. It is categorised as a Execute tool in the Specky MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Specky MCP server in PolicyLayer and add a rule for sdd_setup_local_env: 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_setup_local_env is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sdd_setup_local_env 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_setup_local_env. 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_setup_local_env 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.