AI agents use stack_submit to create or update resources in MCP DevTools Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP DevTools Server environment.
Creating pull requests modifies repository state by introducing new proposed changes. While not destructive (pull requests are reversible and don't execute in production), this is a Write operation with high severity due to potential for submitting malicious, buggy, or otherwise harmful code to a development workflow. The 'entire stack' scope amplifies the blast radius.
From the tool's definition Tool name 'stack_submit' and description 'Submit entire stack as pull requests' indicate the tool creates new pull requests, which are write operations that introduce code changes into a repository.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access stack_submit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stack_submit:
{
"version": "1",
"default": "deny",
"tools": {
"stack_submit": {
"limits": [
{
"counter": "stack_submit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}stack_submit 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.
Submit entire stack as pull requests. It is categorised as a Write tool in the MCP DevTools Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for stack_submit: 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 MCP DevTools Server. Nothing to install.
stack_submit 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 stack_submit 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 stack_submit. 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.
stack_submit is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools 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.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.