AI agents call get_stored_procedure_definition 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) |
formatOutput | boolean | — | Format the SQL output for better readability (default: true) |
procedureName | string | Yes | Name of the stored procedure to get definition for |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
This tool retrieves and queries the definition/source code of a stored procedure, which is a read-only operation with no side effects. However, severity is medium rather than low because exposed stored procedure source code can reveal sensitive business logic, security vulnerabilities, database schema details, or credentials embedded in the code—information useful for reconnaissance or further attacks.
From the tool's definition Tool name 'get_stored_procedure_definition' and description 'Get the complete SQL query/definition of a stored procedure - this is the actual source code' indicate retrieval of existing stored procedure source code with no modification or execution of the…
Attacks that exploit this kind of access
Get the complete SQL query/definition of a stored procedure - this is the actual source code. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
get_stored_procedure_definition accepts 5 parameters: schema, formatOutput, procedureName, connectionName, connectionString. Required: procedureName. 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_stored_procedure_definition: 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_stored_procedure_definition 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_stored_procedure_definition 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_stored_procedure_definition. 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_stored_procedure_definition 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.
get_stored_procedure_definition is one line of Mssql's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →