memory_restore_by_tag · Junto Memory MCP: Risk & Policy

WHAT IT DOES

What memory_restore_by_tag does on Junto Memory

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

WHY IT NEEDS A POLICY

Why memory_restore_by_tag needs a policy

An AI agent can call memory_restore_by_tag faster than any human can review — one bad instruction and it creates or modifies resources in Junto Memory by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_restore_by_tag Rate-limited

memory_restore_by_tag 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": {
    "memory_restore_by_tag": {
      "limits": [
        {
          "counter": "memory_restore_by_tag_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 Junto Memory, so you can run agents against it safely.

FAQ

Questions about memory_restore_by_tag

What does the memory_restore_by_tag tool do? +

memory_restore_by_tag. It is categorised as a Write tool in the Junto Memory 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_restore_by_tag? +

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

What risk level is memory_restore_by_tag? +

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

Can I rate-limit memory_restore_by_tag? +

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

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

memory_restore_by_tag is provided by the Junto Memory MCP server (tlemmons/junto-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.