Check the status of the AWS RDS certificate cache
AI agents call check_certificate_cache to retrieve information from MCP PostgreSQL Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the status of a cached certificate, which is a read-only query operation. It has no capability to modify certificates, trigger AWS operations, or cause side effects. The blast radius of misuse is minimal—an attacker could only learn about certificate cache status, not compromise credentials or perform actions in AWS.
From the tool's definition Tool name is 'check_certificate_cache' and description states 'Check the status' — both indicate a query/inspection operation with no modification or execution of external operations.
Attacks that exploit this kind of access
Check the status of the AWS RDS certificate cache. It is categorised as a Read tool in the MCP PostgreSQL Server MCP Server, which means it retrieves data without modifying state.
Register the MCP PostgreSQL Server MCP server in PolicyLayer and add a rule for check_certificate_cache: 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 PostgreSQL Server. Nothing to install.
check_certificate_cache 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 check_certificate_cache 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 check_certificate_cache. 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.
check_certificate_cache is provided by the MCP PostgreSQL Server MCP server (kristofer84/mcp-postgres). 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 →