AI agents use create_pivot_table to create or update resources in Office Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Office Editor environment.
Creating a pivot table modifies the document by adding a new analytical structure, but this is reversible (pivot tables can be deleted). It does not execute arbitrary code, delete data irreversibly, or move money. The risk is medium because improper pivot table creation could obscure data or cause analytical errors, but the operation itself is inherently non-destructive and bounded within document modification.
From the tool's definition Tool name 'create_pivot_table' indicates creation of a new pivot table structure in an Excel workbook. Server context describes 'creating and editing...Excel' documents.
Documented attack patterns abuse exactly the kind of access create_pivot_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Office Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for create_pivot_table:
{
"version": "1",
"default": "deny",
"tools": {
"create_pivot_table": {
"limits": [
{
"counter": "create_pivot_table_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_pivot_table 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_pivot_table. It is categorised as a Write tool in the Office Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Office Editor MCP server in PolicyLayer and add a rule for create_pivot_table: 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 Office Editor. Nothing to install.
create_pivot_table 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_pivot_table 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_pivot_table. 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_pivot_table is provided by the Office Editor MCP server (thewdy/office-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Office Editor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Office Editor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.