Medium Risk

create_memory

Create a new memory with optional type-specific metadata

How to control create_memory ↓

What create_memory does on AGI MCP Server

AI agents use create_memory to create or update resources in AGI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AGI MCP Server environment.

Medium Risk

Why create_memory needs a policy

This tool creates new records in a persistent memory system. Creation is a Write operation—it modifies the system state reversibly. Severity is medium because misuse could allow an AI agent to inject false memories, manipulate its own reasoning chain, or pollute the knowledge base it relies upon for decision-making, but the effects are not irreversible (memories can be archived/deleted) and do not directly execute…

From the tool's definition Tool name 'create_memory' and description 'Create a new memory' indicate data creation. The phrase 'with optional type-specific metadata' confirms modification of the memory system's state.

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

How to control create_memory

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

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

create_memory 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 AGI MCP Server — 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 create_memory

What does the create_memory tool do? +

Create a new memory with optional type-specific metadata. It is categorised as a Write tool in the AGI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_memory? +

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

What risk level is create_memory? +

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

Can I rate-limit create_memory? +

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

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

create_memory is provided by the AGI MCP Server MCP server (quixiai/agi-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 AGI MCP Server tool call.

Start from AGI MCP Server, 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.

24 AGI MCP Server 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.