AI agents use save_excel_workbook 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.
Saving a workbook commits modifications to disk, making changes permanent and affecting shared files or data sources. This is a Write operation (reversible via undo/version control) rather than Destructive, but carries high severity because unintended saves could corrupt or overwrite important financial data, formulas, or analysis in Excel documents commonly used for critical business operations.
From the tool's definition Tool name 'save_excel_workbook' indicates saving/persisting modifications to an Excel file. Server context confirms it edits Excel documents. Empty description limits precision but name and server purpose clearly indicate data persistence.
Documented attack patterns abuse exactly the kind of access save_excel_workbook 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 save_excel_workbook:
{
"version": "1",
"default": "deny",
"tools": {
"save_excel_workbook": {
"limits": [
{
"counter": "save_excel_workbook_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_excel_workbook 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.
save_excel_workbook. 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 save_excel_workbook: 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.
save_excel_workbook 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 save_excel_workbook 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 save_excel_workbook. 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.
save_excel_workbook 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.