# update_logical_view

Updates a Bigtable logical view within a specified instance. You can update the GoogleSQL query and/or the deletion protection setting. At least one field to update (e.g., query or deletion_protection) must be provided in logical_view field. Update query example: { "project_id": "my-project", "instance_id": "my-instance", "logical_view_id": "my-logical-view", logical_view: { "query": "SELECT CF FROM my-table" } } Update deletion protection example: { "project_id": "my-project", "instance_id": "my-instance", "logical_view_id": "my-logical-view", logical_view: { "deletion_protection": true } } Update query and deletion protection example: { "project_id": "my-project", "instance_id": "my-instance", "logical_view_id": "my-logical-view", logical_view: { "query": "SELECT CF FROM my-table", "deletion_protection": true } }

Agent View of the PolicyLayer registry record for `update_logical_view`. HTML page: https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/update-logical-view

## Facts

- Tool: `update_logical_view`
- Server: Mcp (`https://bigtableadmin.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp.md
- Homepage: https://github.com/https://bigtableadmin.googleapis.com/mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 4 (4 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `projectId` | string | yes | Required. The project ID (e.g., "my-project"). If not known from the context, the Agent should attempt to get the current project ID from the gcloud config by r |
| `instanceId` | string | yes | Required. The instance ID within the project where the logical view will be created (e.g., "my-instance"). |
| `logicalView` | object | yes | Required. The logical view to update. |
| `logicalViewId` | string | yes | Required. The ID used for the logical view within its instance, e.g., `mylogicalview`. |

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": "update_logical_view",
    "arguments": {
      "projectId": "<projectId>",
      "instanceId": "<instanceId>",
      "logicalView": {},
      "logicalViewId": "<logicalViewId>"
    }
  }
}
```

## Why update_logical_view is rated Medium

This tool modifies existing data (the logical view configuration) but the changes are reversible—queries and deletion protection settings can be updated again or reverted. It does not delete data, execute arbitrary code, or commit financial transactions. The impact is limited to metadata updates within a controlled schema, making it a Write operation.

From the tool's own definition: "Updates a Bigtable logical view within a specified instance. You can update the GoogleSQL query and/or the deletion protection setting."

## Use case

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

## Recommended policy (PolicyLayer)

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

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

## Other tools on Mcp (13)

- `delete_instance` — Destructive — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/delete-instance.md
- `delete_logical_view` — Destructive — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/delete-logical-view.md
- `delete_table` — Destructive — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/delete-table.md
- `get_instance` — Read — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/get-instance.md
- `get_logical_view` — Read — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/get-logical-view.md
- `get_table` — Read — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/get-table.md
- `list_hot_tablets` — Read — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/list-hot-tablets.md
- `list_instances` — Read — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/list-instances.md
- `list_logical_views` — Read — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/list-logical-views.md
- `list_tables` — Read — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/list-tables.md
- `create_instance` — Write — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/create-instance.md
- `create_logical_view` — Write — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/create-logical-view.md
- `create_table` — Write — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/create-table.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=com-googleapis-bigtableadmin-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-bigtableadmin-mcp