Parameters of a stored procedure. Accepts bare or schema.procedure identifiers (e.g. dbo.usp_UpdateUser).
AI agents call describe_procedure to retrieve information from Mssql Mcp Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dbKey | string | — | Database key (lowercased). Optional in single-database mode. Call `list_databases` to discover valid keys. |
procedure | string | Yes |
Parameters from the server's own tool schema.
This is a metadata inspection tool. It reads stored procedure definitions and parameters without executing them, modifying data, or triggering side effects. It belongs in the Read category with low severity since exposure poses minimal risk—an agent can only learn about procedure signatures, not execute arbitrary code or modify data.
From the tool's definition Tool name 'describe_procedure' and description 'Parameters of a stored procedure' indicate it retrieves metadata about stored procedure signatures. No execution, modification, or deletion occurs—it only queries and returns parameter information.
Attacks that exploit this kind of access
Parameters of a stored procedure. Accepts bare or schema.procedure identifiers (e.g. dbo.usp_UpdateUser). It is categorised as a Read tool in the Mssql Mcp Node MCP Server, which means it retrieves data without modifying state.
describe_procedure accepts 2 parameters: dbKey, procedure. Required: procedure. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql Mcp Node MCP server in PolicyLayer and add a rule for describe_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 Mcp Node. Nothing to install.
describe_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_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_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_procedure is provided by the Mssql Mcp Node MCP server (mssql-mcp-node). 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 →