Set the number of header columns on a table. Header columns get special styling. Set to 0 to remove header column styling.
AI agents use numbers_set_header_columns to create or update resources in Iwork — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iwork environment.
This tool modifies document metadata (header column count and styling) in a Numbers spreadsheet. The changes are reversible—header styling can be removed or changed at any time without destroying data. This is a write operation (modification of existing structure) rather than execute (no code/command execution), destructive (no permanent deletion), or other categories.
From the tool's definition Tool description states "Set the number of header columns on a table" and "Set to 0 to remove header column styling" — these are reversible modifications to document formatting/structure within Numbers.
Documented attack patterns abuse exactly the kind of access numbers_set_header_columns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iwork, and nothing reaches the server without passing your rules. This is the rule we recommend for numbers_set_header_columns:
{
"version": "1",
"default": "deny",
"tools": {
"numbers_set_header_columns": {
"limits": [
{
"counter": "numbers_set_header_columns_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} numbers_set_header_columns 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.
Set the number of header columns on a table. Header columns get special styling. Set to 0 to remove header column styling. It is categorised as a Write tool in the Iwork MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iwork MCP server in PolicyLayer and add a rule for numbers_set_header_columns: 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 Iwork. Nothing to install.
numbers_set_header_columns 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 numbers_set_header_columns 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 numbers_set_header_columns. 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.
numbers_set_header_columns is provided by the Iwork MCP server (reichenbach/iwork_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iwork, 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.
114 Iwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.