Low Risk

memory_retrieve_records

memory_retrieve_records

How to control memory_retrieve_records ↓

What memory_retrieve_records does on Awslabs Amazon Sns Sqs

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

Low Risk

Why memory_retrieve_records needs a policy

The name suggests a query/retrieval operation characteristic of Read tools (no data modification or deletion). However, the complete absence of a description introduces significant uncertainty about the tool's actual behavior and potential side effects. The confidence is reduced due to lack of supporting documentation.

From the tool's definition Tool name 'memory_retrieve_records' contains the verb 'retrieve', which aligns with Read operations. However, the description is empty, which prevents validation of whether it actually retrieves data or has side effects.

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

How to control memory_retrieve_records

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 memory_retrieve_records:

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

memory_retrieve_records 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 Awslabs Amazon Sns Sqs — 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 memory_retrieve_records

What does the memory_retrieve_records tool do? +

memory_retrieve_records. 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 memory_retrieve_records? +

Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for memory_retrieve_records: 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 memory_retrieve_records? +

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

Can I rate-limit memory_retrieve_records? +

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

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

memory_retrieve_records 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.

Free to start. No card required.

805 Awslabs Amazon Sns Sqs 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.