Soft-delete a page by moving it to _trash/<YYYY-MM>/<original-path>. Recoverable from within SilverBullet itself. Always confirm with the user before calling. Returns the trash path so the user can find the moved file if they want to restore it.
AI agents call delete_page to permanently remove resources in Silverbullet — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the deletion is soft (recoverable), it irreversibly removes pages from the user's active workspace. The tool instructions to 'Always confirm with the user before calling' acknowledge the destructive nature. This is categorized as Destructive rather than Write because it removes data from the user's working context, not merely modifying it.
From the tool's definition Tool description states 'Soft-delete a page by moving it to _trash' — this is a delete operation that removes data from its original location.
Attacks that exploit this kind of access
Soft-delete a page by moving it to _trash/<YYYY-MM>/<original-path>. Recoverable from within SilverBullet itself. Always confirm with the user before calling. Returns the trash path so the user can find the moved file if they want to restore it. It is categorised as a Destructive tool in the Silverbullet MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Silverbullet MCP server in PolicyLayer and add a rule for delete_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 Silverbullet. Nothing to install.
delete_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 delete_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 delete_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.
delete_page is provided by the Silverbullet MCP server (xmatthewx/silverbullet-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 →