Medium Risk

memory_create

memory_create

How to control memory_create ↓

What memory_create does on Awslabs Amazon Sns Sqs

AI agents use memory_create to create or update resources in Awslabs Amazon Sns Sqs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Amazon Sns Sqs environment.

Medium Risk

Why memory_create needs a policy

The tool name indicates a write/create operation that modifies state by adding a new memory entry. Without further description, we cannot determine if this is reversible (write) or irreversible (destructive). Given the ambiguity, Write is the most conservative classification.

From the tool's definition Tool name 'memory_create' suggests creating or storing data, consistent with Write operations. However, the description is empty, limiting certainty about exact behavior and potential scope of modification.

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

How to control memory_create

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_create": {
      "limits": [
        {
          "counter": "memory_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

memory_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about memory_create

What does the memory_create tool do? +

memory_create. It is categorised as a Write tool in the Awslabs Amazon Sns Sqs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_create? +

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

memory_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_create? +

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

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

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