snow_create_mobile_action · Serac MCP: Risk & Policy

WHAT IT DOES

What snow_create_mobile_action does on Serac

AI agents invoke snow_create_mobile_action 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 IT NEEDS A POLICY

Why snow_create_mobile_action needs a policy

The tool creates mobile actions that can execute scripts, which constitutes code execution capability. Even though 'create' sounds like Write, the fact that these actions can execute scripts elevates the risk category to Execute. The blast radius is high because malicious or misconfigured mobile actions could be triggered by users across the organization via the mobile app.

From the tool's definition Actions can navigate, execute scripts, or open forms

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

snow_create_mobile_action Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snow_create_mobile_action": {
      "limits": [
        {
          "counter": "snow_create_mobile_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about snow_create_mobile_action

What does the snow_create_mobile_action tool do? +

Creates a mobile action that users can trigger from the mobile app. Actions can navigate, execute scripts, or open forms. 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.

How do I enforce a policy on snow_create_mobile_action? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_create_mobile_action: 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.

What risk level is snow_create_mobile_action? +

snow_create_mobile_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit snow_create_mobile_action? +

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

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

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

// THE FULL RECORD

snow_create_mobile_action is one line of Serac's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →