AI agents use update_page_content 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.
This tool modifies data reversibly by updating page content in OneNote. It does not delete data (which would be Destructive), execute arbitrary code (Execute), nor move money (Financial). The severity is medium because unintended modifications to important notes could disrupt workflows, but the change is reversible through OneNote's version history and undo mechanisms.
From the tool's definition Tool name 'update_page_content' and description 'Update the content of an existing OneNote page' indicate modification of existing data.
Documented attack patterns abuse exactly the kind of access update_page_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Onenote, and nothing reaches the server without passing your rules. This is the rule we recommend for update_page_content:
{
"version": "1",
"default": "deny",
"tools": {
"update_page_content": {
"limits": [
{
"counter": "update_page_content_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_page_content 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.
Free to start. No card required.
Update the content of an existing OneNote 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.
Register the Onenote 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 Onenote. 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 Onenote MCP server (purpleslurple/onenote-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Onenote tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Onenote tools catalogued and risk-classified — across an index of 42,500+ MCP servers.