getDatabaseStats
AI agents call getDatabaseStats to retrieve information from Amazon ElastiCache Memcached MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistics from an ElastiCache Memcached cluster. 'Get' operations that fetch metadata or metrics are Read category operations—they query state without modifying or executing arbitrary operations. No data is deleted, modified, or financial consequences.
From the tool's definition Tool name 'getDatabaseStats' indicates retrieval of database statistics without modification. Description is empty, but the name and context (ElastiCache Memcached server) suggest a diagnostic/observability operation that queries metrics and performance data…
Attacks that exploit this kind of access
getDatabaseStats. It is categorised as a Read tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for getDatabaseStats: 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 Amazon ElastiCache Memcached MCP Server. Nothing to install.
getDatabaseStats 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 getDatabaseStats 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 getDatabaseStats. 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.
getDatabaseStats is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.