raw_request
Escape hatch to call any Google Sheets API v4 path directly, for requests the typed tools don't cover — e.g. a batchUpdate with mergeCells, named ranges, banding, basic filters, slicers, sortRange, findReplace, gradient conditional-format rules, developer metadata, or several requests in one atom...
This record as markdown: /tools/a1-x-tech-mcp-google-sheets/raw-request.md
What raw_request does on Mcp Google Sheets
AI agents invoke raw_request to trigger actions in Mcp Google Sheets. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | JSON request body (POST/PUT only). |
path | string | Yes | API path relative to https://sheets.googleapis.com, e.g. "v4/spreadsheets/<id>:batchUpdate". |
method | string | — | HTTP method (the Sheets API uses only these three). Defaults to GET. |
Parameters from the server's own tool schema.
Why raw_request is rated High
Arbitrary API access enables read, write, destructive, or bulk operations with no restrictions.
From the tool's definition call any Google Sheets API v4 path directly, for requests
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs raw_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Sheets, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For raw_request, this is the rule to start with:
raw_request stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Sheets, apply this rule, and every raw_request call is checked against it from then on.
Questions about raw_request
Escape hatch to call any Google Sheets API v4 path directly, for requests the typed tools don't cover — e.g. a batchUpdate with mergeCells, named ranges, banding, basic filters, slicers, sortRange, findReplace, gradient conditional-format rules, developer metadata, or several requests in one atomic call: path "v4/spreadsheets/<spreadsheetId>:batchUpdate", method POST, body {"requests":[...]}. The path may carry a query string. The Bearer token is added automatically; the method defaults to GET (values updates use PUT). Sheets API paths only — Drive paths are not reachable here. It is categorised as a Execute tool in the Mcp Google Sheets MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
raw_request accepts 3 parameters: body, path, method. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Sheets MCP server in PolicyLayer and add a rule for raw_request: 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 Mcp Google Sheets. Nothing to install.
raw_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the raw_request 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 raw_request. 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.
raw_request is provided by the Mcp Google Sheets MCP server (@a1-x-tech/mcp-google-sheets). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Sheets, and thousands of servers like it.
Across the catalogue