AI agents use create_workbook to create or update resources in Excel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Excel MCP Server environment.
This tool creates new data (a workbook) but does not modify or delete existing data, nor does it execute arbitrary code or move money. It is reversible—a created workbook can be deleted. The severity is medium because creating a new workbook has limited blast radius unless the AI agent maliciously creates many workbooks to consume resources, but this is not a primary concern.
From the tool's definition Tool name 'create_workbook' and description 'Create a new Excel workbook' indicate creation of a new file/data structure. The server description confirms it performs 'create, read, write, format' operations on Excel files.
Documented attack patterns abuse exactly the kind of access create_workbook gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Excel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_workbook:
{
"version": "1",
"default": "deny",
"tools": {
"create_workbook": {
"limits": [
{
"counter": "create_workbook_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Create a new Excel workbook. It is categorised as a Write tool in the Excel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Excel MCP Server MCP server in PolicyLayer and add a rule for create_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 Excel MCP Server. Nothing to install.
create_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 create_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 create_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.
create_workbook is provided by the Excel MCP Server MCP server (mort-lab/excel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Excel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Excel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.