One-time setup tool. Creates the ContextCore Google Sheet with all required columns.
AI agents use setup_contextcore_sheets 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 a new Google Sheet, which is a write operation that modifies the user's Google Drive state by adding a new resource. It is reversible (the sheet can be deleted), so it does not qualify as Destructive.
From the tool's definition Tool description states it 'Creates the ContextCore Google Sheet with all required columns.' The verb 'Creates' indicates data is being written/generated in Google Drive.
Attacks that exploit this kind of access
One-time setup tool. Creates the ContextCore Google Sheet with all required columns. 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 setup_contextcore_sheets: 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.
setup_contextcore_sheets 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 setup_contextcore_sheets 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 setup_contextcore_sheets. 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.
setup_contextcore_sheets 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 →