numbers_rename_sheet
Rename a sheet in place. Numbers does NOT allow duplicate sheet names; the call fails with errJxa when the new name is taken.
This record as markdown: /tools/heznpc-airmcp/numbers-rename-sheet.md
What numbers_rename_sheet does on AirMCP
AI agents use numbers_rename_sheet to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why numbers_rename_sheet is rated Medium
This tool modifies metadata of a Numbers spreadsheet by renaming a sheet. It is categorized as Write because: (1) it creates/modifies data reversibly—a sheet name can be changed again; (2) it does not execute arbitrary code, delete data, or move money; (3) the blast radius is medium because renaming sheets could cause confusion or break references if automation depends on specific sheet names, but the operation is…
From the tool's definition Tool name 'numbers_rename_sheet' and description 'Rename a sheet in place' indicate a modification operation. The description explicitly states the tool renames sheets, which is a reversible write operation (sheets can be renamed back).
Attacks that exploit this kind of access
The rule that runs numbers_rename_sheet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For numbers_rename_sheet, this is the rule to start with:
numbers_rename_sheet 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 AirMCP, apply this rule, and every numbers_rename_sheet call is checked against it from then on.
Questions about numbers_rename_sheet
Rename a sheet in place. Numbers does NOT allow duplicate sheet names; the call fails with errJxa when the new name is taken. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air MCP server in PolicyLayer and add a rule for numbers_rename_sheet: 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 AirMCP. Nothing to install.
numbers_rename_sheet 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_rename_sheet 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_rename_sheet. 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_rename_sheet is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue