create_working_memory

THE RISK

Medium Risk

Why create_working_memory needs a policy

This tool creates new data structures (working memory entries) in a mutable store, which is a Write operation. It does not retrieve data (Read), execute arbitrary code (Execute), permanently destroy data (Destructive), or move money (Financial). The temporary, auto-expiring nature prevents this from being Destructive.

From the tool's definition Tool description states it 'Create[s] a temporary working memory' which is a create operation that modifies state by adding new working memory entries.

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

POLICY

How to control create_working_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_working_memory:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_working_memory": {
      "limits": [
        {
          "counter": "create_working_memory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AGI MCP Server tools

Destructive prune_memories Permanently delete memories based on criteria Destructive cleanup_expired_working_memory Clean up expired working memories Write consolidate_working_memory Consolidate multiple working memories into a single semantic memory Write activate_cluster Activate a memory cluster and get its associated memories Write archive_old_memories Archive old memories based on age and importance criteria Write create_memory Create a new memory with optional type-specific metadata Write create_memory_cluster Create a new memory cluster Write create_memory_relationship Create a relationship between two memories

All 24 AGI MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_working_memory

What does the create_working_memory tool do? +

Create a temporary working memory with expiration. 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_working_memory? +

Register the AGI MCP Server MCP server in PolicyLayer and add a rule for create_working_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_working_memory? +

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

Can I rate-limit create_working_memory? +

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

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

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

CHECK YOUR STACK →