verify_memory · Tages MCP: Risk & Policy

WHAT IT DOES

What verify_memory does on Tages

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

WHY IT NEEDS A POLICY

Why verify_memory needs a policy

This tool modifies the state of a memory entry, transitioning it from 'pending' to 'live'. This is a reversible write operation (the memory could potentially be archived or deleted later), not destructive. The blast radius is medium since promoting incorrect memories could pollute the context injected into future sessions, leading to bad coding decisions.

From the tool's definition Verify a pending auto-extracted memory — promotes it to live so it appears in recall results

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verify_memory Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tages, so you can run agents against it safely.

FAQ

Questions about verify_memory

What does the verify_memory tool do? +

Verify a pending auto-extracted memory — promotes it to live so it appears in recall results. It is categorised as a Write tool in the Tages MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on verify_memory? +

Register the Tages MCP server in PolicyLayer and add a rule for verify_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 Tages. Nothing to install.

What risk level is verify_memory? +

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

Can I rate-limit verify_memory? +

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

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

verify_memory is provided by the Tages MCP server (ryantlee25-droid/tages). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.