# delete_table

Delete a table. The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}/tables/{table}'. Example: { "name": "projects/my-project/instances/my-instance/tables/my-table" } The table must exist. You can use list_tables to verify. Before executing the deletion, you MUST confirm the action with the user by stating the full table name and asking for "yes/no" confirmation.

Agent View of the PolicyLayer registry record for `delete_table`. HTML page: https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/delete-table

## Facts

- Tool: `delete_table`
- 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: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | yes | Required. The unique name of the table to be deleted. Values are of the form `projects/{project}/instances/{instance}/tables/{table}`. |

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": "delete_table",
    "arguments": {
      "name": "<name>"
    }
  }
}
```

## Why delete_table is rated Critical

The delete_table tool permanently removes a table and its data without the ability to recover it. This is an irreversible destructive operation that qualifies as 'Destructive' per the classification rules. While the tool includes a user confirmation requirement as a safeguard, the underlying capability is still to permanently delete data.

From the tool's own definition: "Tool name is 'delete_table' and description states 'Delete a table.' This operation irreversibly removes data from a Google Bigtable resource."

## Use case

AI agents call delete_table 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.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_table"
  ]
}
```

## 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
- `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
- `update_logical_view` — Write — https://policylayer.com/tools/com-googleapis-bigtableadmin-mcp/update-logical-view.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