Create a brand-new page. Errors if the page already exists — use write_page if you intend to overwrite. Returns the resulting {path, lastModified}, leaving the caller write-ready for a follow-up write_page. Path is validated; cannot write into _trash/. Body is capped at 256 KB.
AI agents use create_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.
create_page adds new data to the note space but does not delete or overwrite existing pages (it errors if the page exists). The operation is reversible via delete_page. While it creates content, the blast radius is limited to note creation and is medium rather than high/critical since it cannot directly harm external systems or permanently destroy data. The 256 KB body cap and path validation further limit risk.
From the tool's definition Tool description states 'Create a brand-new page' and 'returns the resulting {path, lastModified}, leaving the caller write-ready for a follow-up write_page'. This is a creation operation that modifies data reversibly.
Attacks that exploit this kind of access
Create a brand-new page. Errors if the page already exists — use write_page if you intend to overwrite. Returns the resulting {path, lastModified}, leaving the caller write-ready for a follow-up write_page. Path is validated; cannot write into _trash/. Body is capped at 256 KB. 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 create_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.
create_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 create_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 create_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.
create_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 →