Get the full DDL of a trigger
AI agents call get_trigger_ddl 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 the SQL definition of a database trigger—a schema introspection operation with no side effects. It does not execute the trigger, modify database state, or alter schema. The operation is purely informational, fitting the 'Read' category. Low severity because exposure of trigger DDL poses minimal risk; it may reveal internal logic but causes no data loss or unauthorized modifications.
From the tool's definition Tool name 'get_trigger_ddl' and description 'Get the full DDL of a trigger' indicate retrieval of trigger definition metadata. DDL (Data Definition Language) queries are read-only operations that retrieve schema information without modifying or executing code.
Attacks that exploit this kind of access
Get the full DDL of a trigger. 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 get_trigger_ddl: 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.
get_trigger_ddl 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_trigger_ddl 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_trigger_ddl. 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_trigger_ddl 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 →