AI agents invoke mcp_execute_procedure to trigger actions in Mcpql. 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.
Stored procedures are executable code units that can contain any SQL logic, including modifications to data, execution of extended stored procedures, or triggering of external operations. While the tool itself doesn't inherently delete data (which would be Destructive), it enables execution of arbitrary stored procedure logic whose effects depend on what the procedure contains.
From the tool's definition Tool name contains 'execute' and description states 'Execute a SQL Server stored procedure with parameters and return results'.
Attacks that exploit this kind of access
Execute a SQL Server stored procedure with parameters and return results. It is categorised as a Execute tool in the Mcpql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcpql MCP server in PolicyLayer and add a rule for mcp_execute_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 Mcpql. Nothing to install.
mcp_execute_procedure 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 mcp_execute_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 mcp_execute_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.
mcp_execute_procedure is provided by the Mcpql MCP server (mcpql). 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 →