Low Risk

cache_get

Get a value from the cache. Args: key: The key to retrieve Returns: Value or error message

How to control cache_get ↓

What cache_get does on AWS

AI agents call cache_get to retrieve information from AWS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why cache_get needs a policy

This is a straightforward cache retrieval operation that queries data without side effects. It takes a key as input and returns a value or error message, which is a typical Read operation. No data is modified, deleted, or executed. Severity is low because misuse would only expose cached data that the requester may already have access to.

From the tool's definition Tool name is 'cache_get' and description states it retrieves 'a value from the cache' with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access cache_get gives an agent:

How to control cache_get

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_get:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cache_get": {}
  }
}

cache_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register AWS — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cache_get

What does the cache_get tool do? +

Get a value from the cache. Args: key: The key to retrieve Returns: Value or error message. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cache_get? +

Register the AWS MCP server in PolicyLayer and add a rule for cache_get: 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. Nothing to install.

What risk level is cache_get? +

cache_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cache_get? +

Yes. Add a rate_limit block to the cache_get 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.

How do I block cache_get completely? +

Set action: deny in the PolicyLayer policy for cache_get. 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.

What MCP server provides cache_get? +

cache_get is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS tool call.

Start from AWS, 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.

300 AWS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.