list_stored_procedures
List all stored procedures in the current database.
This record as markdown: /tools/mukul975-mysql-mcp-server/list-stored-procedures.md
What list_stored_procedures does on Mysql
AI agents call list_stored_procedures to retrieve information from Mysql without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_stored_procedures is rated Low
This tool retrieves and displays information about stored procedures (a read-only query). It has no side effects, does not modify data, and does not execute code. The blast radius of misuse is minimal — an attacker gains visibility into stored procedures but cannot alter them or execute arbitrary code through this tool alone. Classified as Read with low severity.
From the tool's definition Tool name is 'list_stored_procedures' and description states 'List all stored procedures in the current database' — a query operation that retrieves metadata without modifying any data.
Attacks that exploit this kind of access
The rule that runs list_stored_procedures 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 list_stored_procedures, this is the rule to start with:
list_stored_procedures is read-only, so it stays allowed. 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 list_stored_procedures call is checked against it from then on.
Questions about list_stored_procedures
List all stored procedures in the current database. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for list_stored_procedures: 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.
list_stored_procedures is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_stored_procedures 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 list_stored_procedures. 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.
list_stored_procedures 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.
This server
Across the catalogue