AI agents call describe_stored_procedure 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) |
procedureName | string | Yes | Name of the stored procedure to describe |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
includeDefinition | boolean | — | Include the procedure definition/body (default: true) |
Parameters from the server's own tool schema.
This tool retrieves and queries stored procedure metadata (parameters, definition, source code) from the database schema. It performs no modifications, executions, or side effects—it is purely informational. While stored procedure definitions could theoretically contain sensitive business logic, this is a read-only introspection operation.
From the tool's definition Tool name 'describe_stored_procedure' and description 'Get detailed information about a specific stored procedure including parameters and definition' indicate retrieval of metadata without modification or execution.
Attacks that exploit this kind of access
Get detailed information about a specific stored procedure including parameters and definition. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
describe_stored_procedure accepts 5 parameters: schema, procedureName, connectionName, connectionString, includeDefinition. 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 describe_stored_procedure: 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.
describe_stored_procedure 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 describe_stored_procedure 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 describe_stored_procedure. 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.
describe_stored_procedure 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 →