Get detailed information about a stored procedure including its definition
AI agents call describe_procedure to retrieve information from MSSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays metadata about a stored procedure (its definition and properties) without creating, modifying, deleting, or executing it. It is a schema inspection operation with no side effects, consistent with other read operations like describe_table and describe_view on the same server.
From the tool's definition Tool name 'describe_procedure' and description 'Get detailed information about a stored procedure including its definition' indicate data retrieval without modification. The verb 'describe' and 'get' are read-only operations.
Documented attack patterns abuse exactly the kind of access describe_procedure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MSSQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for describe_procedure:
{
"version": "1",
"default": "deny",
"tools": {
"describe_procedure": {}
}
} describe_procedure is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a stored procedure including its definition. It is categorised as a Read tool in the MSSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MSSQL MCP Server 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 Server. 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 Server MCP server (jensenloke/mcp-sqlserver-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MSSQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 MSSQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.