list_tables
List all tables in a specified instance. The request requires the 'parent' field to be set in the format 'projects/{project}/instances/{instance}'. Example: { "parent": "projects/my-project/instances/my-instance" }
This record as markdown: /tools/com-googleapis-bigtableadmin-mcp/list-tables.md
What list_tables does on Mcp
AI agents call list_tables to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
view | string | — | The view to be applied to the returned tables' fields. Only NAME_ONLY view (default), REPLICATION_VIEW and ENCRYPTION_VIEW are supported. |
parent | string | Yes | Required. The unique name of the instance for which tables should be listed. Values are of the form `projects/{project}/instances/{instance}`. |
pageSize | integer | — | Maximum number of results per page. A page_size of zero lets the server choose the number of items to return. A page_size which is strictly positive will return |
pageToken | string | — | The value of `next_page_token` returned by a previous call. |
Parameters from the server's own tool schema.
Why list_tables is rated Low
This tool queries and returns a list of existing tables without modifying, deleting, or executing any operations. It is a read-only retrieval operation with minimal security risk, appropriate for low severity. Confidence is high because the name and description clearly indicate a list/query action.
From the tool's definition Tool name is 'list_tables' and description states 'List all tables in a specified instance' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_tables 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 list_tables, this is the rule to start with:
list_tables is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_tables call is checked against it from then on.
Questions about list_tables
List all tables in a specified instance. The request requires the 'parent' field to be set in the format 'projects/{project}/instances/{instance}'. Example: { "parent": "projects/my-project/instances/my-instance" }. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_tables accepts 4 parameters: view, parent, pageSize, pageToken. Required: parent. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for list_tables: 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.
list_tables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_tables 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.
Set action: deny in the PolicyLayer policy for list_tables. 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.
list_tables 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.
This server
Across the catalogue