Move a page to a new location (read → create destination → delete source). Refuses if the destination already exists. If the source was edited between the read and the delete, the delete is skipped — leaving a recoverable duplicate at the destination rather than losing interim edits. Does NOT rew...
AI agents use move_page to create or update resources in Silverbullet — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Silverbullet environment.
While move_page performs both creation and deletion operations, it is fundamentally reversible: the source is retained if edits occur between read and delete ("leaving a recoverable duplicate"), and the destination can be manually deleted. This makes it Write rather than Destructive. The collision detection ("Refuses if the destination already exists") provides additional safety.
From the tool's definition Tool description states: "Move a page to a new location (read → create destination → delete source)". The operation involves creating a new page at destination and deleting the source, which are reversible through recovery or manual restoration of the deleted…
Attacks that exploit this kind of access
Move a page to a new location (read → create destination → delete source). Refuses if the destination already exists. If the source was edited between the read and the delete, the delete is skipped — leaving a recoverable duplicate at the destination rather than losing interim edits. Does NOT rewrite [[backlinks]] — SilverBullet. It is categorised as a Write tool in the Silverbullet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Silverbullet MCP server in PolicyLayer and add a rule for move_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.
move_page 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 move_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 move_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.
move_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 →