New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_logical_view

Deletes a Bigtable logical view within a specified instance. The request requires the name field to be set in the format 'projects/{project}/instances/{instance}/logicalViews/{logical_view}'. Example: { "name": "projects/my-project/instances/my-instance/logicalViews/my-logical-view" } Before exec...

SERVERMcp SOURCEhttps://bigtableadmin.googleapis.com/mcp
Critical RISK CLASS
Category Destructive
Parameters 21 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What delete_logical_view does on Mcp

AI agents call delete_logical_view to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
etag string Optional. The current etag of the logical view. If an etag is provided and does not match the current etag of the logical view, deletion will be blocked and an
name string Yes Required. The unique name of the logical view to be deleted. Format: `projects/{project}/instances/{instance}/logicalViews/{logical_view}`.

Parameters from the server's own tool schema.

Why delete_logical_view is rated Critical

The tool performs an irreversible deletion of a Bigtable logical view resource. While it includes a user confirmation requirement as a safeguard, the underlying action is destructive and cannot be recovered once executed. This places it in the Destructive category rather than Write.

From the tool's definition Tool name is 'delete_logical_view' and description states 'Deletes a Bigtable logical view' - this is an irreversible deletion operation that cannot be undone.

Questions about delete_logical_view

What does the delete_logical_view tool do? +

Deletes a Bigtable logical view within a specified instance. The request requires the name field to be set in the format 'projects/{project}/instances/{instance}/logicalViews/{logical_view}'. Example: { "name": "projects/my-project/instances/my-instance/logicalViews/my-logical-view" } Before executing the deletion, you MUST confirm the action with the user by stating the full logical view name and asking for "yes/no" confirmation. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does delete_logical_view accept? +

delete_logical_view accepts 2 parameters: etag, name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on delete_logical_view? +

Register the MCP server in PolicyLayer and add a rule for delete_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 delete_logical_view? +

delete_logical_view is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_logical_view? +

Yes. Add a rate_limit block to the delete_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 delete_logical_view completely? +

Set action: deny in the PolicyLayer policy for delete_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 delete_logical_view? +

delete_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.

More on , and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.