AI agents call get_key_type to retrieve information from Redis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves key metadata (type and time-to-live information) from Redis without modifying, executing, or deleting any data. It is a pure Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_key_type' and description '获取键的类型和TTL' (retrieve key type and TTL) indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
获取键的类型和TTL. It is categorised as a Read tool in the Redis MCP Server, which means it retrieves data without modifying state.
Register the Redis MCP server in PolicyLayer and add a rule for get_key_type: 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 Redis. Nothing to install.
get_key_type 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 get_key_type 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 get_key_type. 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.
get_key_type is provided by the Redis MCP server (lm203688/redis-mcp-server). 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 →