snow_create_vulnerability_scan
Creates vulnerability scanning configurations. Schedules scans, sets severity thresholds, and enables auto-remediation.
This record as markdown: /tools/serac/snow-create-vulnerability-scan.md
What snow_create_vulnerability_scan does on Serac
AI agents invoke snow_create_vulnerability_scan 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_create_vulnerability_scan is rated High
This tool does more than just write configuration data — it schedules automated scans (triggering recurring external operations) and can enable auto-remediation, which means it can autonomously trigger remediation actions based on scan findings. The auto-remediation capability in particular represents an Execute-level risk, as it initiates operations whose effects depend on the scan results and thresholds configured.
From the tool's definition Creates vulnerability scanning configurations. Schedules scans, sets severity thresholds, and enables auto-remediation.
Attacks that exploit this kind of access
The rule that runs snow_create_vulnerability_scan 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_create_vulnerability_scan, this is the rule to start with:
snow_create_vulnerability_scan 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_create_vulnerability_scan call is checked against it from then on.
Questions about snow_create_vulnerability_scan
Creates vulnerability scanning configurations. Schedules scans, sets severity thresholds, and enables auto-remediation. 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_create_vulnerability_scan: 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_create_vulnerability_scan 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_create_vulnerability_scan 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_create_vulnerability_scan. 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_create_vulnerability_scan 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