generate_snowflake_table

WHAT IT DOES

What generate_snowflake_table does on Claude MCP Data Engineer Server

AI agents use generate_snowflake_table to create or update resources in Claude MCP Data Engineer Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude MCP Data Engineer Server environment.

WHY IT NEEDS A POLICY

Why generate_snowflake_table needs a policy

This tool creates new database tables, which is a reversible write operation. While CREATE TABLE does modify database structure, it is not destructive (tables can be dropped) and does not delete or overwrite existing data. The severity is medium because misuse could create unwanted tables consuming storage and resources, but the impact is recoverable.

From the tool's definition Tool generates a 'CREATE TABLE statement' for Snowflake, which creates new database objects. The description explicitly mentions table generation with optional clustering keys, indicating DDL execution that modifies schema.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_snowflake_table Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude MCP Data Engineer Server, so you can run agents against it safely.

FAQ

Questions about generate_snowflake_table

What does the generate_snowflake_table tool do? +

Generate a Snowflake CREATE TABLE statement with optional clustering keys. It is categorised as a Write tool in the Claude MCP Data Engineer Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_snowflake_table? +

Register the Claude MCP Data Engineer Server MCP server in PolicyLayer and add a rule for generate_snowflake_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 Claude MCP Data Engineer Server. Nothing to install.

What risk level is generate_snowflake_table? +

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

Can I rate-limit generate_snowflake_table? +

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

How do I block generate_snowflake_table completely? +

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

What MCP server provides generate_snowflake_table? +

generate_snowflake_table is provided by the Claude MCP Data Engineer Server MCP server (itsnikhile/claude-mcp-data-engineer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.