AI agents use create_stored_procedure to create or update resources in Mcp Windows — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Windows environment.
Creating a stored procedure writes a new persistent database object. However, stored procedures can contain arbitrary SQL including destructive operations (DELETE, DROP), making this potentially a vector for Execute or Destructive actions at runtime. The act of creation itself is Write, but the blast radius is high because a maliciously crafted stored procedure could later cause significant harm.
From the tool's definition 'Create a stored procedure' - creates a new database object
Documented attack patterns abuse exactly the kind of access create_stored_procedure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for create_stored_procedure:
{
"version": "1",
"default": "deny",
"tools": {
"create_stored_procedure": {
"limits": [
{
"counter": "create_stored_procedure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_stored_procedure 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.
Create a stored procedure. It is categorised as a Write tool in the Mcp Windows MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for create_stored_procedure: 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 Windows. Nothing to install.
create_stored_procedure 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 create_stored_procedure 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 create_stored_procedure. 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.
create_stored_procedure is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.