AI agents use excel_set_borders to create or update resources in Excel — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Excel environment.
Setting borders modifies spreadsheet formatting (a Write operation) without destroying data or executing arbitrary code. The change is reversible—borders can be removed or changed. Severity is medium because misuse could corrupt visual formatting across large ranges, affecting readability and usability of game configuration files, but no data loss or code execution occurs.
From the tool's definition Tool name 'excel_set_borders' and description '设置边框' (set borders) indicate modification of cell formatting properties in an Excel file. This is a reversible structural change to the spreadsheet.
Documented attack patterns abuse exactly the kind of access excel_set_borders gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Excel, and nothing reaches the server without passing your rules. This is the rule we recommend for excel_set_borders:
{
"version": "1",
"default": "deny",
"tools": {
"excel_set_borders": {
"limits": [
{
"counter": "excel_set_borders_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}excel_set_borders 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.
设置边框. It is categorised as a Write tool in the Excel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Excel MCP server in PolicyLayer and add a rule for excel_set_borders: 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. Nothing to install.
excel_set_borders 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_set_borders 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_set_borders. 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_set_borders is provided by the Excel MCP server (tangentdomain/excel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Excel, 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.
36 Excel tools catalogued and risk-classified — across an index of 43,000+ MCP servers.