google_sheet_write_data
AI agents use google_sheet_write_data to create or update resources in ContextCore MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextCore MCP environment.
This tool creates or modifies data in Google Sheets, which is reversible (can be undone/edited). It is categorized as Write rather than Read (no retrieval), Execute (no command/code execution), Destructive (modifications are typically reversible), or Financial (no direct money movement).
From the tool's definition Tool name 'google_sheet_write_data' explicitly indicates data writing to Google Sheets. Description is empty, but the function name is unambiguous: 'write_data' implies creating or modifying spreadsheet content.
Attacks that exploit this kind of access
google_sheet_write_data. It is categorised as a Write tool in the ContextCore MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ContextCore MCP server in PolicyLayer and add a rule for google_sheet_write_data: 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 ContextCore MCP. Nothing to install.
google_sheet_write_data 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 google_sheet_write_data 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 google_sheet_write_data. 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.
google_sheet_write_data is provided by the ContextCore MCP server (rkpraveendev/contextcore-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 →