knowledge_supersede · Loom MCP: Risk & Policy

WHAT IT DOES

What knowledge_supersede does on Loom

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

WHY IT NEEDS A POLICY

Why knowledge_supersede needs a policy

This is a Write operation because it creates or modifies data reversibly—marking supersession and archiving are state transitions that can be undone or reverted. It is not Destructive because archiving typically preserves data rather than permanently erasing it.

From the tool's definition Tool performs two reversible operations: 'Mark one knowledge page as superseded by another' and 'archive the old page.' These actions modify metadata and move/archive data rather than permanently deleting it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

knowledge_supersede Rate-limited

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

FAQ

Questions about knowledge_supersede

What does the knowledge_supersede tool do? +

Mark one knowledge page as superseded by another, then archive the old page. It is categorised as a Write tool in the Loom MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on knowledge_supersede? +

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

What risk level is knowledge_supersede? +

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

Can I rate-limit knowledge_supersede? +

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

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

knowledge_supersede is provided by the Loom MCP server (jbarket/loom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.