Create a new Google Sheets document.
AI agents use create_spreadsheet to create or update resources in Google Connections — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Connections environment.
Creating a new spreadsheet is a reversible write operation that modifies the state of Google Workspace by adding a new document. While it consumes resources and may clutter a user's Drive, it does not permanently delete data, execute arbitrary code, or commit financial obligations.
From the tool's definition Tool name 'create_spreadsheet' and description 'Create a new Google Sheets document' indicate data creation without deletion or financial impact. The server description confirms CRUD operations including creation.
Attacks that exploit this kind of access
Create a new Google Sheets document. It is categorised as a Write tool in the Google Connections MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Connections MCP server in PolicyLayer and add a rule for 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 Google Connections. Nothing to install.
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 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 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.
create_spreadsheet is provided by the Google Connections MCP server (michaelzrork/google-connections-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 →