snow_elevate_role
Execute a server-side operation that requires elevated privileges (security_admin scope — ACL modifications, high-security properties, etc.). ALWAYS returns a confirmation prompt on the first call; executes only when re-called with user_confirmed=true. Agents cannot skip this confirmation.
This record as markdown: /tools/serac/snow-elevate-role.md
What snow_elevate_role does on Serac
AI agents invoke snow_elevate_role to trigger actions in Serac. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why snow_elevate_role is rated High
This tool runs server-side operations that modify access control lists and security properties. While it has a confirmation safeguard (user_confirmed=true requirement), it is fundamentally an Execute category tool because it triggers external operations (ACL modifications, privilege elevation) whose effects depend on what elevated operation is being performed.
From the tool's definition Tool description states: 'Execute a server-side operation that requires elevated privileges (security_admin scope — ACL modifications, high-security properties, etc.)'.
Attacks that exploit this kind of access
The rule that runs snow_elevate_role safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_elevate_role, this is the rule to start with:
snow_elevate_role stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_elevate_role call is checked against it from then on.
Questions about snow_elevate_role
Execute a server-side operation that requires elevated privileges (security_admin scope — ACL modifications, high-security properties, etc.). ALWAYS returns a confirmation prompt on the first call; executes only when re-called with user_confirmed=true. Agents cannot skip this confirmation. It is categorised as a Execute tool in the Serac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Serac MCP server in PolicyLayer and add a rule for snow_elevate_role: 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 Serac. Nothing to install.
snow_elevate_role is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the snow_elevate_role 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 snow_elevate_role. 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.
snow_elevate_role is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
Across the catalogue