Create a new Google Spreadsheet. Returns ID and URL.
AI agents use drive_create_spreadsheet to create or update resources in Gworkspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gworkspace environment.
Creating a new spreadsheet is a Write operation—it generates data that can be reversed by deleting the spreadsheet. It has no destructive effects, does not execute arbitrary code, and does not involve financial transactions. The blast radius is minimal, as the worst-case misuse would be creation of unwanted spreadsheet files, which are easily deletable.
From the tool's definition Tool name 'drive_create_spreadsheet' and description 'Create a new Google Spreadsheet' indicate a create operation that generates a new, reversible resource.
Attacks that exploit this kind of access
Create a new Google Spreadsheet. Returns ID and URL. It is categorised as a Write tool in the Gworkspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gworkspace MCP server in PolicyLayer and add a rule for drive_create_spreadsheet: 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 Gworkspace. Nothing to install.
drive_create_spreadsheet 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_create_spreadsheet 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_create_spreadsheet. 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_create_spreadsheet is provided by the Gworkspace MCP server (leoonic/gworkspace-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 →