cache_get_many

THE RISK

Low Risk

Why cache_get_many needs a policy

This tool retrieves cached data without modifying, deleting, or executing operations. The 'get' verb and the description clearly indicate a read-only operation. Low severity because the blast radius of misuse is limited to information disclosure of cached data.

From the tool's definition Tool name 'cache_get_many' and description 'Get multiple values from the cache' indicate a retrieval operation with no side effects.

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

POLICY

How to control cache_get_many

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cache_get_many": {}
  }
}

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

Create a free account and register Awslabs Amazon Sns Sqs — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Awslabs Amazon Sns Sqs tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint

All 805 Awslabs Amazon Sns Sqs tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about cache_get_many

What does the cache_get_many tool do? +

Get multiple values from the cache. It is categorised as a Read tool in the Awslabs Amazon Sns Sqs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cache_get_many? +

Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for cache_get_many: 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 Awslabs Amazon Sns Sqs. Nothing to install.

What risk level is cache_get_many? +

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

Can I rate-limit cache_get_many? +

Yes. Add a rate_limit block to the cache_get_many 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_many completely? +

Set action: deny in the PolicyLayer policy for cache_get_many. 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_many? +

cache_get_many is provided by the Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Awslabs Amazon Sns Sqs tool call.

Start from Awslabs Amazon Sns Sqs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →