Analyzes the performance characteristics of a CQL query - args: keyspace, query
AI agents call analyzeQueryPerformance to retrieve information from AWS Labs postgres MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only diagnostic tool that examines query performance metrics. It takes a keyspace and query string as input and returns analysis data. There are no side effects mentioned, no data modification, no code execution on external systems, and no destructive operations. The most severe category that applies is Read, as the tool retrieves and reports performance characteristics.
From the tool's definition Analyzes the performance characteristics of a CQL query - args: keyspace, query. The tool name and description indicate it performs analysis/profiling of existing queries without modifying, deleting, or executing any query logic.
Documented attack patterns abuse exactly the kind of access analyzeQueryPerformance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs postgres MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyzeQueryPerformance:
{
"version": "1",
"default": "deny",
"tools": {
"analyzeQueryPerformance": {}
}
}analyzeQueryPerformance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyzes the performance characteristics of a CQL query - args: keyspace, query. It is categorised as a Read tool in the AWS Labs postgres MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS Labs postgres MCP Server MCP server in PolicyLayer and add a rule for analyzeQueryPerformance: 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 AWS Labs postgres MCP Server. Nothing to install.
analyzeQueryPerformance 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 analyzeQueryPerformance 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 analyzeQueryPerformance. 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.
analyzeQueryPerformance is provided by the AWS Labs postgres MCP Server MCP server (awslabs.postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs postgres MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS Labs postgres MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.