// MCP TOOL REFERENCE

chainmemory_seal

Seal a memory permanently. Can never be modified after sealing.

Part of the Chainmemory MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

chainmemory-mcp Destructive Risk 4/5

// WHEN AI AGENTS USE THIS TOOL

AI agents may call chainmemory_seal to permanently remove or destroy resources in Chainmemory. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON CHAINMEMORY_SEAL

Without a policy, an AI agent could call chainmemory_seal in a loop, permanently destroying resources in Chainmemory. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-chaelynet-chainmemory.yaml

tools:
  chainmemory_seal:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Chainmemory policy for all 6 tools.

// DETAILS

Tool Name chainmemory_seal

Category Destructive

MCP Server Chainmemory MCP Server

Risk Level Critical

// MORE CHAINMEMORY TOOLS

Write chainmemory_register Write chainmemory_remember Read chainmemory_profile Read chainmemory_recall Read chainmemory_stats

// WHAT CAN GO WRONG

Agents calling destructive-class tools like chainmemory_seal have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete Agent Passport System — Cryptographic Identity for AI Agents remove_intent_card Agent Passport System — Cryptographic Identity for AI Agents revoke_delegation

// IN CONTEXT OF CRITICAL RISK

chainmemory_seal is one of the critical-risk operations in Chainmemory. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the chainmemory_seal tool do? +

Seal a memory permanently. Can never be modified after sealing.. It is categorised as a Destructive tool in the Chainmemory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on chainmemory_seal? +

Add a rule in your Intercept YAML policy under the tools section for chainmemory_seal. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Chainmemory MCP server.

What risk level is chainmemory_seal? +

chainmemory_seal is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit chainmemory_seal? +

Yes. Add a rate_limit block to the chainmemory_seal rule in your Intercept 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 chainmemory_seal completely? +

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

chainmemory_seal is provided by the Chainmemory MCP server (chainmemory-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

chainmemory_seal

Enforce policies on Chainmemory