update_logical_view

SERVERMcp SOURCEhttps://bigtableadmin.googleapis.com/mcp

Medium RISK CLASS

Category Write

Parameters 44 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-bigtableadmin-mcp/update-logical-view.md

WHAT IT DOES

What update_logical_view does on Mcp

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.

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.

RISK

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 definition Updates a Bigtable logical view within a specified instance. You can update the GoogleSQL query and/or the deletion protection setting.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_logical_view safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_logical_view, this is the rule to start with:

update_logical_view Rate-limited

update_logical_view stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every update_logical_view call is checked against it from then on.

FAQ

Questions about update_logical_view

What does the update_logical_view tool do? +

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 } }. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_logical_view accept? +

update_logical_view accepts 4 parameters: projectId, instanceId, logicalView, logicalViewId. Required: projectId, instanceId, logicalView, logicalViewId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_logical_view? +

Register the MCP server in PolicyLayer and add a rule for update_logical_view: 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. Nothing to install.

What risk level is update_logical_view? +

update_logical_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_logical_view? +

Yes. Add a rate_limit block to the update_logical_view 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.

How do I block update_logical_view completely? +

Set action: deny in the PolicyLayer policy for update_logical_view. 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.

What MCP server provides update_logical_view? +

update_logical_view is provided by the MCP server (https://bigtableadmin.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 14 tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →