create_instance

SERVERMcp SOURCEhttps://bigtableadmin.googleapis.com/mcp

Medium RISK CLASS

Category Write

Parameters 44 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-bigtableadmin-mcp/create-instance.md

WHAT IT DOES

What create_instance does on Mcp

AI agents use create_instance to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.

Parameter	Type	Required	Description
`clusters`	array	Yes	Required. Clusters to be created within the instance. At least one cluster must be specified.
`projectId`	string	Yes	Required. The project ID (e.g., "my-project"). If not known from the context, the Agent should attempt to get the current project ID from the gcloud config by r
`instanceId`	string	Yes	Required. The ID to be used when referring to the new instance within its project, e.g., just `myinstance` rather than `projects/myproject/instances/myinstance`
`displayName`	string	Yes	Required. The descriptive name for this instance as it appears in UIs.

Parameters from the server's own tool schema.

RISK

Why create_instance is rated Medium

Creating a new Bigtable instance is a write operation that establishes new infrastructure and incurs cloud resource costs. It is reversible (instances can be deleted via delete_instance), so it falls under Write rather than Destructive.

From the tool's definition Tool creates a new instance in the specified project with cluster configuration, which is a reversible data/resource creation operation. Description states 'Create a new instance' and requires project_id, instance_id, display_name, and cluster specifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_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 create_instance, this is the rule to start with:

create_instance Rate-limited

create_instance stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_instance": {
      "limits": [
        {
          "counter": "create_instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every create_instance call is checked against it from then on.

FAQ

Questions about create_instance

What does the create_instance tool do? +

Create a new instance in the specified project. The request requires project_id, instance_id, display_name, and at least one cluster. The instance_id must be RFC 1035 compliant. Each cluster must specify its zone (e.g. us-central1-a). Example: { "project_id": "my-project", "instance_id": "my-instance", "display_name": "This is my instance", "clusters": [ { "zone": "us-central1-a", "serve_nodes": 3, "default_storage_type": "SSD" } ] }. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_instance accept? +

create_instance accepts 4 parameters: clusters, projectId, instanceId, displayName. Required: clusters, projectId, instanceId, displayName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_instance? +

Register the MCP server in PolicyLayer and add a rule for create_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.

What risk level is create_instance? +

create_instance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_instance? +

Yes. Add a rate_limit block to the create_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.

How do I block create_instance completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_instance? +

create_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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 14 tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →