Get the definition/source code of a stored procedure
AI agents call get_procedure_definition to retrieve information from LocalDB 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 the source code definition of an existing stored procedure. It is a read-only operation that queries database schema metadata without creating, modifying, deleting, or executing any code. The action has no side effects on the database or data—it merely inspects existing procedure definitions.
From the tool's definition Tool name 'get_procedure_definition' and description 'Get the definition/source code of a stored procedure' indicate retrieval of stored procedure metadata/source code with no modification or execution of the procedure itself.
Attacks that exploit this kind of access
Get the definition/source code of a stored procedure. It is categorised as a Read tool in the LocalDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LocalDB MCP Server MCP server in PolicyLayer and add a rule for get_procedure_definition: 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 LocalDB MCP Server. Nothing to install.
get_procedure_definition 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_definition 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_definition. 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_definition is provided by the LocalDB MCP Server MCP server (sam2332/localdb-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 →