Get the full CREATE PROCEDURE source code for a stored procedure, including its parameters and body.
AI agents call get_stored_procedure_definition to retrieve information from Sql Database without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
server | string | Yes | Server hostname (e.g. server1.database.windows.net) |
database | string | Yes | Database name |
procedure_name | string | Yes | Name of the stored procedure (optionally schema-qualified, e.g. dbo.MyProc) |
Parameters from the server's own tool schema.
This tool only retrieves the definition/source code of an existing stored procedure. It does not create, modify, delete, or execute procedures. It performs a query/inspection operation similar to sibling tools like 'get_table_schema' and 'list_stored_procedures', which are Read operations. The blast radius is minimal: an agent could learn procedure logic but cannot alter data or execute code through this tool alone.
From the tool's definition Tool name is 'get_stored_procedure_definition' and description states 'Get the full CREATE PROCEDURE source code' — purely retrieves and returns existing procedure metadata without modification or execution.
Attacks that exploit this kind of access
Get the full CREATE PROCEDURE source code for a stored procedure, including its parameters and body. It is categorised as a Read tool in the Sql Database MCP Server, which means it retrieves data without modifying state.
get_stored_procedure_definition accepts 3 parameters: server, database, procedure_name. Required: server, database, procedure_name. The full parameter table on this page comes from the server's own tool schema.
Register the Sql Database 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 Sql Database. 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 Sql Database MCP server (sql-database-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 →