This record as markdown: /tools/mukul975-mysql-mcp-server/create-stored-procedure.md
What create_stored_procedure does on Mysql
AI agents invoke create_stored_procedure to trigger actions in Mysql. 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.
Why create_stored_procedure is rated High
Creating a stored procedure installs executable code into the database. While the act of creation is a Write, stored procedures can encapsulate arbitrary SQL including DML, DDL, and destructive operations. The most severe applicable category is Execute, as this tool introduces persistent executable logic into the database environment.
From the tool's definition "Create a stored procedure" - creates executable database code that can be invoked later to run arbitrary SQL logic
Attacks that exploit this kind of access
The rule that runs create_stored_procedure safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_stored_procedure, this is the rule to start with:
create_stored_procedure 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql, apply this rule, and every create_stored_procedure call is checked against it from then on.
Questions about create_stored_procedure
Create a stored procedure. It is categorised as a Execute tool in the Mysql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mysql 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 Mysql. Nothing to install.
create_stored_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 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 Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
Across the catalogue