knowledge_move · Loom MCP: Risk & Policy

WHAT IT DOES

What knowledge_move does on Loom

AI agents use knowledge_move 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_move needs a policy

The tool modifies knowledge page organization and routing (re-keying/re-domaining) but does not delete, destroy, or irreversibly transform data—the uuid and citations remain intact. This qualifies as Write (reversible modification) rather than Destructive.

From the tool's definition Tool description states "Re-key or re-domain a knowledge page in place" which modifies metadata/structure of existing data (re-keying, re-domaining) while explicitly preserving the underlying record ("same row, same uuid").

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

knowledge_move Rate-limited

knowledge_move 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_move": {
      "limits": [
        {
          "counter": "knowledge_move_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_move

What does the knowledge_move tool do? +

Re-key or re-domain a knowledge page in place — same row, same uuid, citations and verification history preserved. 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_move? +

Register the Loom MCP server in PolicyLayer and add a rule for knowledge_move: 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_move? +

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

Can I rate-limit knowledge_move? +

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

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

knowledge_move 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.