AI agents use excel_set_row_height 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 row height modifies the spreadsheet but does not delete data, execute code, or move money. It is a formatting operation that can be undone, placing it in the Write category. Severity is medium because unintended batch row height changes could obscure data or corrupt the visual structure of game configuration files managed by designers, but the impact is reversible and non-destructive.
From the tool's definition Tool name 'excel_set_row_height' and description '设置行高' (Chinese: 'set row height') indicate a modification operation on Excel spreadsheet formatting. This is a reversible change to spreadsheet structure/appearance.
Documented attack patterns abuse exactly the kind of access excel_set_row_height 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_row_height:
{
"version": "1",
"default": "deny",
"tools": {
"excel_set_row_height": {
"limits": [
{
"counter": "excel_set_row_height_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}excel_set_row_height 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_row_height: 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_row_height 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_row_height 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_row_height. 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_row_height 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.