create_table
Create a new table in the specified instance.
This record as markdown: /tools/com-googleapis-bigtableadmin-mcp/create-table.md
What create_table does on Mcp
AI agents use create_table 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 |
|---|---|---|---|
tableId | string | Yes | Required. The ID to be used when referring to the new table within its instance, e.g., just `mytable`. |
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 instance ID within the project where the table will be created (e.g., "my-instance"). |
columnFamilies | array | — | Optional. The names of the column families to be created in the table. Example: `["cf1", "cf2"]`. The tool mapping will apply a default garbage collection polic |
Parameters from the server's own tool schema.
Why create_table is rated Medium
This tool creates new data structures (tables) in Google Bigtable, which is a reversible write operation. While it modifies the database schema, it does not execute arbitrary code, delete data, or move money. Severity is medium because creating tables can consume resources and affect application behavior, but the operation is reversible via the sibling delete_table tool.
From the tool's definition Tool name 'create_table' and description 'Create a new table in the specified instance' indicate data creation.
Attacks that exploit this kind of access
The rule that runs create_table 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_table, this is the rule to start with:
create_table 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every create_table call is checked against it from then on.
Questions about create_table
Create a new table in the specified instance. 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.
create_table accepts 4 parameters: tableId, projectId, instanceId, columnFamilies. Required: tableId, projectId, instanceId. 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 create_table: 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.
create_table is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_table 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 create_table. 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.
create_table 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