insert_blocks · Mnemosyne MCP: Risk & Policy

WHAT IT DOES

What insert_blocks does on Mnemosyne MCP

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

WHY IT NEEDS A POLICY

Why insert_blocks needs a policy

The name 'insert_blocks' and context of knowledge graph management suggest this tool adds or modifies data blocks within the Mnemosyne graph system. This is a Write operation (creates or modifies data reversibly). Severity is high because inserting blocks into a knowledge graph could corrupt data integrity if misused, though the operation is reversible.

From the tool's definition Tool name 'insert_blocks' combined with sibling tools like 'create_graph', 'create_wires', and 'create_folder' indicates it creates or modifies data structures. The parent server description states it enables agents to 'create, and manage' knowledge graphs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_blocks Rate-limited

insert_blocks 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": {
    "insert_blocks": {
      "limits": [
        {
          "counter": "insert_blocks_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 Mnemosyne MCP, so you can run agents against it safely.

FAQ

Questions about insert_blocks

What does the insert_blocks tool do? +

insert_blocks. It is categorised as a Write tool in the Mnemosyne MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on insert_blocks? +

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

What risk level is insert_blocks? +

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

Can I rate-limit insert_blocks? +

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

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

insert_blocks is provided by the Mnemosyne MCP server (sophia-labs/mnemosyne-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.