Create a new table with specified columns
AI agents use create_table to create or update resources in Snowflake Developer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Snowflake Developer MCP Server environment.
create_table creates new database objects (tables) with specified schemas. This is reversible via drop_table operations, making it Write rather than Destructive. Severity is high because incorrect table creation can impact data organization, storage costs, and application functionality in a production Snowflake environment. Confidence is high due to explicit naming and clear intent.
From the tool's definition Tool name 'create_table' and description 'Create a new table with specified columns' indicate data structure creation.
Attacks that exploit this kind of access
Create a new table with specified columns. It is categorised as a Write tool in the Snowflake Developer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Snowflake Developer MCP Server 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 Snowflake Developer MCP Server. 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 Snowflake Developer MCP Server MCP server (mcp-tg/snowflake-developer-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →