merge_data · Snowflake Developer MCP Server MCP

WHAT IT DOES

What merge_data does on Snowflake Developer MCP Server

AI agents use merge_data 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.

WHY IT NEEDS A POLICY

Why merge_data needs a policy

MERGE is a write operation that modifies table data through conditional inserts, updates, or deletes. While MERGE can delete rows as part of its operation, it is primarily a data synchronization tool and less severe than tools explicitly named delete_data or drop_database_object. The operation is reversible through standard database transaction controls.

From the tool's definition Tool performs MERGE operation to 'synchronize data between tables,' which is a SQL DML statement that creates or modifies data reversibly. MERGE can INSERT, UPDATE, or DELETE rows based on join conditions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_data Rate-limited

merge_data 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": {
    "merge_data": {
      "limits": [
        {
          "counter": "merge_data_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 Snowflake Developer MCP Server, so you can run agents against it safely.

FAQ

Questions about merge_data

What does the merge_data tool do? +

Perform a MERGE operation to synchronize data between tables. 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.

How do I enforce a policy on merge_data? +

Register the Snowflake Developer MCP Server MCP server in PolicyLayer and add a rule for merge_data: 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.

What risk level is merge_data? +

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

Can I rate-limit merge_data? +

Yes. Add a rate_limit block to the merge_data 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 merge_data completely? +

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

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