Write or replace content on a page using the native Y.js WebSocket protocol. Accepts markdown (recommended) or structured content blocks. Supports: headings (H1/H2/H3), paragraphs, bold, italic, strikethrough, underline, inline code, links, highlight, bullet/numbered/checkbox lists, dividers, blo...
AI agents use update_page_content to create or update resources in Fusebase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusebase MCP Server environment.
This tool creates or modifies data reversibly - it updates page content which can be edited, reverted, or overwritten by subsequent calls. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not move money (would be Financial).
From the tool's definition Tool name explicitly states 'update_page_content' and description says 'Write or replace content on a page' using Y.js WebSocket protocol. Accepts various markdown and structured content formats.
Attacks that exploit this kind of access
Write or replace content on a page using the native Y.js WebSocket protocol. Accepts markdown (recommended) or structured content blocks. Supports: headings (H1/H2/H3), paragraphs, bold, italic, strikethrough, underline, inline code, links, highlight, bullet/numbered/checkbox lists, dividers, blockquotes, code blocks (with language), toggles, hints/callouts, collapsible headings, images, files, bookmarks, remote frames, outlines, buttons, steps, tables, and grid layouts. It is categorised as a Write tool in the Fusebase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for update_page_content: 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 Fusebase MCP Server. Nothing to install.
update_page_content 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 update_page_content 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 update_page_content. 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.
update_page_content is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). 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 →