get_instance
Get information about an instance. The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}'. Example: { "name": "projects/my-project/instances/my-instance" }
This record as markdown: /tools/com-googleapis-bigtableadmin-mcp/get-instance.md
What get_instance does on Mcp
AI agents call get_instance 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 instance. Values are of the form `projects/{project}/instances/{instance}`. |
Parameters from the server's own tool schema.
Why get_instance is rated Low
This tool retrieves or queries data about a Google Bigtable instance without modifying, creating, or deleting any resources. It is a pure read operation with no destructive or side-effect-causing capabilities. The blast radius is low as it only exposes existing instance information. Confidence is high because the intent and behavior are unambiguous.
From the tool's definition Tool name 'get_instance' and description 'Get information about an instance' indicate a retrieval operation with no side effects. The operation requires only a 'name' field to query existing instance metadata.
Attacks that exploit this kind of access
The rule that runs get_instance 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_instance, this is the rule to start with:
get_instance 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_instance call is checked against it from then on.
Questions about get_instance
Get information about an instance. The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}'. Example: { "name": "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.
get_instance 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_instance: 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_instance 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_instance 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_instance. 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_instance 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