get_procedure_parameters

THE RISK

Low Risk

Why get_procedure_parameters needs a policy

This tool retrieves metadata about stored procedure parameters. It queries database schema information without creating, modifying, deleting, or executing any code or data operations. This is a passive inspection operation with no side effects, fitting the Read category. Low severity because schema introspection poses minimal risk even if abused by an AI agent.

From the tool's definition Tool description states 'Get parameter information for a stored procedure' — a retrieval operation with no modification or execution of code.

Documented attack patterns abuse exactly the kind of access get_procedure_parameters gives an agent:

POLICY

How to control get_procedure_parameters

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 get_procedure_parameters:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_procedure_parameters": {}
  }
}

get_procedure_parameters is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MSSQL MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MSSQL MCP Server tools

Destructive delete_index Delete an index Destructive delete_procedure Delete a stored procedure Destructive delete_view Delete a view Execute execute_procedure Execute a stored procedure with optional parameters Write create_index Create a new index Write create_procedure Create a new stored procedure Write create_table Create a new table in the database Write create_view Create a new view

All 23 MSSQL MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_procedure_parameters

What does the get_procedure_parameters tool do? +

Get parameter information for a stored procedure. It is categorised as a Read tool in the MSSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_procedure_parameters? +

Register the MSSQL MCP 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 MSSQL MCP Server. Nothing to install.

What risk level is get_procedure_parameters? +

get_procedure_parameters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_procedure_parameters? +

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.

How do I block get_procedure_parameters completely? +

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.

What MCP server provides get_procedure_parameters? +

get_procedure_parameters 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.

Enforce policy on every MSSQL MCP Server tool call.

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.

CHECK YOUR STACK →