remnote_set_document_status · Remnote MCP: Risk & Policy

WHAT IT DOES

What remnote_set_document_status does on Remnote

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

WHY IT NEEDS A POLICY

Why remnote_set_document_status needs a policy

This tool modifies metadata of existing Rem entries in the RemNote knowledge base by toggling their document status. It is reversible (status can be toggled back) and does not irreversibly delete data. The dryRun default indicates potential write capability.

From the tool's definition Tool description states it 'set[s] whether an existing Rem is marked as a document' and 'requires write operations to be enabled'. The dryRun parameter indicates it performs state modifications (document status flag) on existing knowledge base elements.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remnote_set_document_status Rate-limited

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

FAQ

Questions about remnote_set_document_status

What does the remnote_set_document_status tool do? +

Preview or set whether an existing Rem is marked as a document. Uses dryRun=true by default, preserves Rem ID, children, parent, tags, and concept/card status, and requires write operations to be enabled. It is categorised as a Write tool in the Remnote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remnote_set_document_status? +

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

What risk level is remnote_set_document_status? +

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

Can I rate-limit remnote_set_document_status? +

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

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

remnote_set_document_status is provided by the Remnote MCP server (remnote-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.