Execute a SQL query against the PostgreSQL database. Supports parameterized queries for safety. Returns rows and row count.
AI agents invoke query to trigger actions in Mcp Postgres Query. 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.
This tool runs arbitrary SQL against a PostgreSQL database. While it mentions parameterized queries for safety (reducing injection risk), it does not restrict the SQL to SELECT statements. An AI agent could issue DROP TABLE, DELETE FROM, UPDATE, or other destructive/modifying statements.
From the tool's definition "Execute a SQL query against the PostgreSQL database" — arbitrary SQL execution including potentially destructive statements like DROP, DELETE, or TRUNCATE
Attacks that exploit this kind of access
Execute a SQL query against the PostgreSQL database. Supports parameterized queries for safety. Returns rows and row count. It is categorised as a Execute tool in the Mcp Postgres Query MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Postgres Query MCP server in PolicyLayer and add a rule for query: 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 Mcp Postgres Query. Nothing to install.
query 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 query 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 query. 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.
query is provided by the Mcp Postgres Query MCP server (lordbasilaiassistant-sudo/mcp-postgres-query). 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 →