excel_create
Creates a new Excel (.xlsx) file with headers and optional data rows.
This record as markdown: /tools/com-local-mcp-local-mcp/excel-create.md
What excel_create does on Local
AI agents use excel_create to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Output path for the .xlsx file |
rows | array | — | Array of row arrays with data (optional) |
confirm | boolean | — | Must be true to create |
headers | array | Yes | Column headers |
Parameters from the server's own tool schema.
Why excel_create is rated Medium
This tool creates new files and populates them with data, which is a reversible write operation. It does not execute code, delete data, or move money. The medium severity reflects that creating files on a user's system could have downstream consequences if an agent creates unwanted files or populates them with incorrect data, but the operation is fundamentally reversible (files can be deleted).
From the tool's definition Tool name 'excel_create' and description 'Creates a new Excel (.xlsx) file' explicitly indicates file creation and data population via 'with headers and optional data rows'.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs excel_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For excel_create, this is the rule to start with:
excel_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every excel_create call is checked against it from then on.
Questions about excel_create
Creates a new Excel (.xlsx) file with headers and optional data rows. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
excel_create accepts 4 parameters: path, rows, confirm, headers. Required: path, headers. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for excel_create: 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 Local. Nothing to install.
excel_create 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 excel_create 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 excel_create. 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.
excel_create is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue