Get parameter information for a stored procedure
AI agents call get_procedure_parameters to retrieve information from SQL Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is purely informational—it queries metadata about stored procedure parameters without executing code, modifying data, or triggering side effects. It fits the Read category pattern of retrieving or querying data for inspection purposes only. The read-only server constraint and the retrieval-only nature of the tool support a low-severity classification.
From the tool's definition Server is described as 'read-only MCP server for SQL Server database introspection' and tool 'get_procedure_parameters' retrieves parameter information for a stored procedure with no modification capability.
Attacks that exploit this kind of access
Get parameter information for a stored procedure. It is categorised as a Read tool in the SQL Server MCP MCP Server, which means it retrieves data without modifying state.
Register the SQL Server MCP server in PolicyLayer and add a rule for get_procedure_parameters: 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 Server MCP. Nothing to install.
get_procedure_parameters 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_procedure_parameters 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_procedure_parameters. 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_procedure_parameters is provided by the SQL Server MCP server (millelog/sql-server-mcp). 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 →