sheet_rename
A write tool on the Mcp Anything MCP server.
This record as markdown: /tools/mcp-anything/sheet-rename.md
What sheet_rename does on Mcp Anything
AI agents use sheet_rename to create or update resources in Mcp Anything, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Anything environment.
Why sheet_rename is rated Medium
The tool performs a reversible modification operation ('rename'). While there is no explicit description, the name strongly suggests it updates a sheet's name or identifier without deleting data. This is categorized as Write rather than Read (has side effects) or Destructive (operation is reversible).
From the tool's definition Tool name 'sheet_rename' indicates modification of a sheet object (likely a spreadsheet or data structure). The 'rename' operation modifies metadata/properties reversibly. No description provided to confirm scope or data impact.
Attacks that exploit this kind of access
The rule that runs sheet_rename safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sheet_rename, this is the rule to start with:
sheet_rename 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 Mcp Anything, apply this rule, and every sheet_rename call is checked against it from then on.
Questions about sheet_rename
sheet_rename is a write tool on the Mcp Anything MCP server. It is categorised as a Write tool in the Mcp Anything MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for sheet_rename: 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 Mcp Anything. Nothing to install.
sheet_rename 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 sheet_rename 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 sheet_rename. 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.
sheet_rename is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue