list_logical_views
List information about all logical views within 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-logical-views.md
What list_logical_views does on Mcp
AI agents call list_logical_views 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 |
|---|---|---|---|
parent | string | Yes | Required. The unique name of the instance for which the list of logical views is requested. Values are of the form `projects/{project}/instances/{instance}`. |
pageSize | integer | — | Optional. The maximum number of logical views to return. The service may return fewer than this value |
pageToken | string | — | Optional. A page token, received from a previous `ListLogicalViews` call. Provide this to retrieve the subsequent page. When paginating, all other parameters pr |
Parameters from the server's own tool schema.
Why list_logical_views is rated Low
This tool queries and returns information about logical views within a Bigtable instance. It performs a read-only operation with no side effects, matching the Read category definition of 'retrieves or queries data'. The severity is low because listing metadata poses minimal risk unless the metadata itself is highly sensitive, which is typical for standard resource enumeration.
From the tool's definition Tool name contains 'list' and description states 'List information about all logical views' — a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs list_logical_views 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_logical_views, this is the rule to start with:
list_logical_views 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_logical_views call is checked against it from then on.
Questions about list_logical_views
List information about all logical views within 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_logical_views accepts 3 parameters: 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_logical_views: 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_logical_views 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_logical_views 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_logical_views. 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_logical_views 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