List stored procedures and/or functions in a database
AI agents call list_routines to retrieve information from Querybridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about stored procedures and functions without executing them, modifying data, or triggering any side effects. It is a read-only introspection capability. The low severity reflects that listing routines reveals database schema information but cannot directly harm data or systems.
From the tool's definition Tool name is 'list_routines' and description states it 'List stored procedures and/or functions in a database' - a pure enumeration/query operation with no modification or execution.
Attacks that exploit this kind of access
List stored procedures and/or functions in a database. It is categorised as a Read tool in the Querybridge MCP Server, which means it retrieves data without modifying state.
Register the Querybridge MCP server in PolicyLayer and add a rule for list_routines: 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 Querybridge. Nothing to install.
list_routines 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 list_routines 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 list_routines. 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.
list_routines is provided by the Querybridge MCP server (mahmoudhassanmustafa/querybridge-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 →