Execute a SQL query on a PostgreSQL database using a configured profile
AI agents invoke dbQuery to trigger actions in Infer MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Executing arbitrary SQL queries can span Read, Write, Destructive, or even Financial actions depending on the query content (SELECT, INSERT, UPDATE, DELETE, DROP, etc.). Since the tool permits arbitrary SQL execution with no stated restrictions, it must be classified at the most severe plausible category. DROP/DELETE statements are possible, making this at minimum Execute and potentially Destructive.
From the tool's definition "Execute a SQL query on a PostgreSQL database" — the tool runs arbitrary SQL against a PostgreSQL database using a configured profile.
Attacks that exploit this kind of access
Execute a SQL query on a PostgreSQL database using a configured profile. It is categorised as a Execute tool in the Infer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infer MCP Server MCP server in PolicyLayer and add a rule for dbQuery: 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 Infer MCP Server. Nothing to install.
dbQuery is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dbQuery 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 dbQuery. 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.
dbQuery is provided by the Infer MCP Server MCP server (jackyxhb/infermcpserver). 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 →