AI agents call get_all_stored_procedure_definitions to retrieve information from Mssql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
schema | string | — | Schema name (default: dbo) |
maxResults | number | — | Maximum number of procedures to return (default: 50, max: 100) |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
includeSystemProcedures | boolean | — | Include system stored procedures (default: false) |
Parameters from the server's own tool schema.
This tool retrieves and queries stored procedure source code without executing them or modifying any data. While the severity is high due to potential exposure of sensitive SQL logic (credentials, business rules, vulnerabilities in stored procedures), the action itself is read-only.
From the tool's definition Tool name is 'get_all_stored_procedure_definitions' and description states 'Get complete SQL definitions for all stored procedures in a schema' — purely retrieval operation with no modification or execution.
Attacks that exploit this kind of access
Get complete SQL definitions for all stored procedures in a schema. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
get_all_stored_procedure_definitions accepts 5 parameters: schema, maxResults, connectionName, connectionString, includeSystemProcedures. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql MCP server in PolicyLayer and add a rule for get_all_stored_procedure_definitions: 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 Mssql. Nothing to install.
get_all_stored_procedure_definitions 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 get_all_stored_procedure_definitions 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 get_all_stored_procedure_definitions. 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.
get_all_stored_procedure_definitions is provided by the Mssql MCP server (mssql-mcp-server). 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 →