Rename a file
AI agents use rename_file to create or update resources in Mail Cal Drive — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mail Cal Drive environment.
Renaming a file is a reversible Write operation. An AI agent with misdirected intent could rename critical files to cause confusion or break application logic (e.g., renaming config files, documents, or attachments in a business context), but the action remains reversible via a second rename.
From the tool's definition Tool name is 'rename_file' with description 'Rename a file'. Renaming modifies file metadata/state but does not delete or destroy the file itself, nor does it execute code or access financial systems.
Attacks that exploit this kind of access
Rename a file. It is categorised as a Write tool in the Mail Cal Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mail Cal Drive MCP server in PolicyLayer and add a rule for rename_file: 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 Mail Cal Drive. Nothing to install.
rename_file 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 rename_file 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 rename_file. 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.
rename_file is provided by the Mail Cal Drive MCP server (rumbitopi/mail-cal-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →