AI agents invoke postgres-execute-query to trigger actions in Mcp Gmail. 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.
A tool that executes arbitrary database queries can perform reads, writes, and destructive operations (DROP, DELETE) depending on arguments. Without restrictions visible in the description, this must be classified as Execute with critical severity due to potential for severe unintended consequences (data deletion, modification, or exposure via a compromised AI agent).
From the tool's definition Tool name 'postgres-execute-query' indicates execution of arbitrary PostgreSQL queries. Empty description limits certainty but naming strongly implies code/query execution capability.
Attacks that exploit this kind of access
postgres-execute-query. It is categorised as a Execute tool in the Mcp Gmail MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for postgres-execute-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 Gmail. Nothing to install.
postgres-execute-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-execute-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-execute-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-execute-query is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →