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/io-github-heznpc-iconnect/numbers-rename-sheet.md
What numbers_rename_sheet does on Iconnect
AI agents use numbers_rename_sheet to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.
Why numbers_rename_sheet is rated Medium
The tool creates or modifies data (the sheet name) reversibly. It updates metadata within the Numbers document without permanently deleting content or executing arbitrary code. While renaming could cause organizational confusion or break external references to sheets, the action is undoable through standard undo functionality in Numbers. This fits the Write category (update).
From the tool's definition 'Rename a sheet in place' directly modifies an existing sheet's name within a Numbers spreadsheet document. The description explicitly states the action is a rename operation, which is a reversible data modification.
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 Iconnect, 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 Iconnect, 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 Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconnect 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 Iconnect. 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 Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue