# manage_protected_ranges

Manages protections that stop other editors from changing cells. action=add protects a grid range (or a named range via named_range_id; a range with only sheet_id protects the whole sheet): warning_only=true merely warns before edits, otherwise only the listed editor_users/editor_groups (emails) plus the owner may edit — note the calling user is NOT added automatically. Returns the new protectedRangeId in the replies. action=update changes description/warning_only/editors of an existing protection (protected_range_id required; provided fields replace the old values). action=delete removes the protection — the cells and data stay, but anyone with edit access can change them again. Find existing protectedRangeIds via get_spreadsheet.

Agent View of the PolicyLayer registry record for `manage_protected_ranges`. HTML page: https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/manage-protected-ranges

## Facts

- Tool: `manage_protected_ranges`
- Server: Mcp Google Sheets (`@a1-x-tech/mcp-google-sheets`) — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets.md
- Install: `npx -y @a1-x-tech/mcp-google-sheets`
- Homepage: https://github.com/A1-x-Tech/mcp-google-sheets
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 9 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `range` | object | no | add: the cells to protect. |
| `action` | string | yes | What to do with the protections. |
| `description` | string | no | Label shown in the Sheets UI protections list. |
| `editor_users` | array | no | Emails of users allowed to edit the protected cells. |
| `warning_only` | boolean | no | true = anyone can still edit after a warning; false = only the listed editors. |
| `editor_groups` | array | no | Emails of Google Groups allowed to edit. |
| `named_range_id` | string | no | add: protect a named range instead of a grid range. |
| `spreadsheet_id` | string | yes | The spreadsheet id — the long id from the URL (docs.google.com/spreadsheets/d/<spreadsheetId>/edit) or from create_spreadsheet / search_spreadsheets output. |
| `protected_range_id` | integer | no | update/delete: the protection's id from get_spreadsheet or the add reply. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "manage_protected_ranges",
    "arguments": {
      "action": "<action>",
      "spreadsheet_id": "<spreadsheet_id>"
    }
  }
}
```

## Why manage_protected_ranges is rated Medium

Modifies spreadsheet access controls and permissions reversibly; does not delete data directly.

From the tool's own definition: "Manages protections that stop other editors from changing cells, add/update/delete"

Risk signals: High parameter count (14 properties)

## Use case

AI agents use manage_protected_ranges to create or update resources in Mcp Google Sheets, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Sheets environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Google Sheets:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_protected_ranges": {
      "limits": [
        {
          "counter": "manage_protected_ranges_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Google Sheets (19)

- `clear_values` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/clear-values.md
- `manage_dimensions` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/manage-dimensions.md
- `manage_sheets` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/manage-sheets.md
- `raw_request` — Execute — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/raw-request.md
- `append_values` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/append-values.md
- `get_spreadsheet` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/get-spreadsheet.md
- `read_values` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/read-values.md
- `search_spreadsheets` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/search-spreadsheets.md
- `batch_write_values` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/batch-write-values.md
- `create_spreadsheet` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/create-spreadsheet.md
- `format_cells` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/format-cells.md
- `manage_charts` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/manage-charts.md
- `manage_conditional_formats` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/manage-conditional-formats.md
- `manage_permissions` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/manage-permissions.md
- `manage_tables` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/manage-tables.md
- `set_borders` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/set-borders.md
- `set_data_validation` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/set-data-validation.md
- `set_frozen` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/set-frozen.md
- `write_values` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-sheets/write-values.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a1-x-tech-mcp-google-sheets · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a1-x-tech-mcp-google-sheets