get_logical_view
Get information about the specified logical view. 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" }
This record as markdown: /tools/com-googleapis-bigtableadmin-mcp/get-logical-view.md
What get_logical_view does on Mcp
AI agents call get_logical_view 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 |
|---|---|---|---|
name | string | Yes | Required. The unique name of the requested logical view. Values are of the form `projects/{project}/instances/{instance}/logicalViews/{logical_view}`. |
Parameters from the server's own tool schema.
Why get_logical_view is rated Low
This tool performs a read-only query operation that retrieves information about a logical view in Google Bigtable. It requires only a name parameter to fetch existing data and has no side effects. This fits the Read category definition of retrieving or querying data with no side effects.
From the tool's definition Tool name is 'get_logical_view' and description states 'Get information about the specified logical view.' The operation retrieves metadata about an existing logical view without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
The rule that runs get_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 get_logical_view, this is the rule to start with:
get_logical_view 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 get_logical_view call is checked against it from then on.
Questions about get_logical_view
Get information about the specified logical view. 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" }. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_logical_view accepts 1 parameter: name. Required: name. 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 get_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.
get_logical_view 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
This server
Across the catalogue