set_context · Snowflake Developer MCP Server MCP

WHAT IT DOES

What set_context does on Snowflake Developer MCP Server

AI agents use set_context 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 set_context needs a policy

This tool changes operational parameters (database, schema, warehouse, role context) which alters how subsequent queries execute. This qualifies as Write because it modifies the active configuration state, though reversibly and without affecting data.

From the tool's definition The tool description states it 'Set the current database context (database, schema, warehouse, role)' - this modifies connection state parameters that affect subsequent operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_context Rate-limited

set_context 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": {
    "set_context": {
      "limits": [
        {
          "counter": "set_context_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 set_context

What does the set_context tool do? +

Set the current database context (database, schema, warehouse, role). 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 set_context? +

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

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

Can I rate-limit set_context? +

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

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

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