memento_share_memory_to_workspace

WHAT IT DOES

What memento_share_memory_to_workspace does on Memento

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

WHY IT NEEDS A POLICY

Why memento_share_memory_to_workspace needs a policy

This tool writes/copies memory data from one workspace to another, creating or modifying data in the target workspace. It is reversible in principle (the share can be undone), so Write is the appropriate category rather than Destructive. The cross-workspace nature elevates severity to medium since misuse could leak context across project boundaries.

From the tool's definition Share a memory with another project workspace for cross-project context

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memento_share_memory_to_workspace Rate-limited

memento_share_memory_to_workspace 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": {
    "memento_share_memory_to_workspace": {
      "limits": [
        {
          "counter": "memento_share_memory_to_workspace_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 Memento, so you can run agents against it safely.

FAQ

Questions about memento_share_memory_to_workspace

What does the memento_share_memory_to_workspace tool do? +

[DEPRECATED] Share a memory with another project workspace for cross-project context. It is categorised as a Write tool in the Memento MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memento_share_memory_to_workspace? +

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

What risk level is memento_share_memory_to_workspace? +

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

Can I rate-limit memento_share_memory_to_workspace? +

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

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

memento_share_memory_to_workspace is provided by the Memento MCP server (joyciakira/memento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.