List all stored procedures in a database
AI agents call list_procedures to retrieve information from SQL Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about stored procedures (names, possibly schemas) without executing them, modifying data, or triggering side effects. It is a non-destructive introspection capability consistent with the server's stated purpose of 'database introspection.' The Read category applies to tools that query or retrieve data; the low severity reflects minimal blast radius—listing procedures does not expose data…
From the tool's definition Tool name is 'list_procedures' and description states it 'List all stored procedures in a database' — a pure enumeration/listing operation with no modification or execution of database content.
Attacks that exploit this kind of access
List all stored procedures in a database. It is categorised as a Read tool in the SQL Server MCP MCP Server, which means it retrieves data without modifying state.
Register the SQL Server MCP server in PolicyLayer and add a rule for list_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 SQL Server MCP. Nothing to install.
list_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_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_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_procedures is provided by the SQL Server MCP server (millelog/sql-server-mcp). 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 →