move_file
AI agents use move_file to create or update resources in Cloudflare Google OAuth MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cloudflare Google OAuth MCP Server environment.
Moving a file modifies its location/path but is reversible (can be moved back). This is a Write operation, not Destructive. Severity is medium because file movement in a shared authenticated system could cause application disruption or unintended access changes, but the operation itself is not irreversible.
From the tool's definition Tool named 'move_file' with empty description; sibling tools on this server include 'delete_file', 'rename_file', and 'upload_file', establishing a file management context. 'move_file' reversibly relocates data without deletion.
Attacks that exploit this kind of access
move_file. It is categorised as a Write tool in the Cloudflare Google OAuth MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cloudflare Google OAuth MCP Server MCP server in PolicyLayer and add a rule for move_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 Cloudflare Google OAuth MCP Server. Nothing to install.
move_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 move_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 move_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.
move_file is provided by the Cloudflare Google OAuth MCP Server MCP server (zxzinn/cf-gdrive-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 →