update_page
Applies one or more edits to an existing OneNote page (append, prepend, insert, replace, delete). Targets are body, title, or #<data-id> selectors — find data-id values in the HTML returned by read_page.
This record as markdown: /tools/1percentlabs-onenote-mcp/update-page.md
What update_page does on Onenote
AI agents use update_page to create or update resources in Onenote, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Onenote environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
pageId | string | Yes | OneNote page ID to update. |
operations | array | Yes | Ordered list of edits to apply to the page in a single request. |
Parameters from the server's own tool schema.
Why update_page is rated Medium
An AI agent can call update_page faster than any human can review: one bad instruction and it creates or modifies resources in Onenote by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (operations[].content)
Attacks that exploit this kind of access
The rule that runs update_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Onenote, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_page, this is the rule to start with:
update_page stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Onenote, apply this rule, and every update_page call is checked against it from then on.
Questions about update_page
Applies one or more edits to an existing OneNote page (append, prepend, insert, replace, delete). Targets are body, title, or #<data-id> selectors — find data-id values in the HTML returned by read_page. It is categorised as a Write tool in the Onenote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_page accepts 2 parameters: pageId, operations. Required: pageId, operations. The full parameter table on this page comes from the server's own tool schema.
Register the Onenote MCP server in PolicyLayer and add a rule for update_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 Onenote. Nothing to install.
update_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 update_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 update_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.
update_page is provided by the Onenote MCP server (@1percentlabs/onenote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Onenote, and thousands of servers like it.
This server
Across the catalogue