Move a page to the archive (soft delete — recoverable from the
AI agents call archive_page to permanently remove resources in Hubnote Mcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although described as a soft delete (recoverable), archiving a page removes it from the active workspace and is closer to a destructive action than a write. The partial description suggests it is recoverable, which lowers severity slightly, but the primary action is removal/hiding of content, fitting the Destructive category. Confidence is slightly reduced due to the truncated description.
From the tool's definition 'Move a page to the archive (soft delete — recoverable from the' — the tool archives/removes a page from active use
Attacks that exploit this kind of access
Move a page to the archive (soft delete — recoverable from the. It is categorised as a Destructive tool in the Hubnote Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hubnote MCP server in PolicyLayer and add a rule for archive_page: 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 Hubnote Mcp. Nothing to install.
archive_page is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the archive_page 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 archive_page. 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.
archive_page is provided by the Hubnote MCP server (wlzerd/hubnote-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 →