Archive a document to hide it from active views.
AI agents use refmd-archive-document to create or update resources in RefMD MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RefMD MCP Server environment.
Archiving is a state change that modifies how a document is displayed but does not irreversibly delete data or prevent recovery. The document remains in the system and can typically be unarchived. This is a Write operation (reversible modification) rather than Destructive (irreversible deletion).
From the tool's definition Tool name 'refmd-archive-document' and description 'Archive a document to hide it from active views' indicate a reversible modification of document state/visibility.
Attacks that exploit this kind of access
Archive a document to hide it from active views. It is categorised as a Write tool in the RefMD MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RefMD MCP Server MCP server in PolicyLayer and add a rule for refmd-archive-document: 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 RefMD MCP Server. Nothing to install.
refmd-archive-document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the refmd-archive-document 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.
Set action: deny in the PolicyLayer policy for refmd-archive-document. 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.
refmd-archive-document is provided by the RefMD MCP Server MCP server (refmdio/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →