AI agents use create_section 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 creates a new organizational unit (section) in OneNote, which is a write operation that modifies the notebook structure. It is reversible (sections can be deleted) and has no permanent destructive effects. The blast radius is limited to the OneNote notebook's organization structure, affecting primarily the user and potentially collaborators with access to that notebook.
From the tool's definition Tool name is 'create_section' and description states 'Create a new section in a OneNote notebook.' The verb 'create' indicates the tool creates new data structures reversibly within OneNote.
Documented attack patterns abuse exactly the kind of access create_section 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 create_section:
{
"version": "1",
"default": "deny",
"tools": {
"create_section": {
"limits": [
{
"counter": "create_section_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_section 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.
Create a new section in a OneNote notebook. 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 create_section: 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.
create_section 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_section 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_section. 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_section 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.