snow_create_vulnerability_scan

Creates vulnerability scanning configurations. Schedules scans, sets severity thresholds, and enables auto-remediation.

Server Serac serac-labs/serac
Category Execute
Risk class High
Parameters 00 required

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 needs a policy

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.

Questions about snow_create_vulnerability_scan

What does the snow_create_vulnerability_scan tool do? +

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.

How do I enforce a policy on snow_create_vulnerability_scan? +

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.

What risk level is snow_create_vulnerability_scan? +

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

Can I rate-limit snow_create_vulnerability_scan? +

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.

How do I block snow_create_vulnerability_scan completely? +

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.

What MCP server provides snow_create_vulnerability_scan? +

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.

// THE FULL RECORD

snow_create_vulnerability_scan 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.