Create a shortcut to a file or folder
AI agents use drive_shortcut_create to create or update resources in Google Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive MCP Server environment.
Creating shortcuts is a reversible write operation that adds new metadata/objects to Google Drive without deleting or overwriting existing data. It modifies the user's Drive organization but can be undone by deleting the shortcut. This is less severe than destructive operations (which cannot be easily reversed) but more severe than simple read operations.
From the tool's definition Tool description states 'Create a shortcut' — a creation operation that modifies Drive's folder structure and file organization by adding new shortcut resources.
Attacks that exploit this kind of access
Create a shortcut to a file or folder. It is categorised as a Write tool in the Google Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for drive_shortcut_create: 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 Google Drive MCP Server. Nothing to install.
drive_shortcut_create 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 drive_shortcut_create 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 drive_shortcut_create. 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.
drive_shortcut_create is provided by the Google Drive MCP Server MCP server (rishipradeep-think41/google-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 →