postgres_query
Run a PostgreSQL query as postgres.
This record as markdown: /tools/mcp-control-plane/postgres-query.md
What postgres_query does on Mcp Control Plane
AI agents invoke postgres_query to trigger actions in Mcp Control Plane. 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.
Why postgres_query is rated High
This tool runs arbitrary SQL queries with superuser (postgres) privileges. It spans Execute, Destructive (DROP/DELETE/TRUNCATE), and potentially Financial categories depending on the database contents. Since it permits arbitrary SQL as a superuser, it is at minimum Execute with Destructive potential, making it critical severity. An AI agent could issue DROP TABLE, DELETE FROM, or exfiltrate sensitive data.
From the tool's definition 'Run a PostgreSQL query as postgres' — executes arbitrary SQL as the superuser postgres account
Attacks that exploit this kind of access
The rule that runs postgres_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For postgres_query, this is the rule to start with:
postgres_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every postgres_query call is checked against it from then on.
Questions about postgres_query
Run a PostgreSQL query as postgres. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for postgres_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 Control Plane. Nothing to install.
postgres_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 postgres_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 postgres_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.
postgres_query is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue