snow_sir_evidence_manage
Unified tool for Security Incident Response (SIR) evidence and forensic artifact chain-of-custody on sn_si_evidence, sn_si_artifact, and sn_si_attachment. Critical for audit trails — every action records who attached/exported the evidence and when. Actions: - attach — attach a new evidence record...
This record as markdown: /tools/serac/snow-sir-evidence-manage.md
What snow_sir_evidence_manage does on Serac
AI agents use snow_sir_evidence_manage to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_sir_evidence_manage is rated Medium
The 'attach' action creates new evidence records linked to SIR incidents, which is a Write operation. While 'list', 'get', and 'hash_verify' are less severe (Read and Execute respectively), the tool's primary risk comes from its ability to attach evidence records to security incidents—this modifies critical forensic data and audit trails in a security-sensitive context.
From the tool's definition The tool performs actions that create and modify data: 'attach — attach a new evidence record' creates records; 'list' and 'get' are read-only but 'attach' and 'hash_verify' modify or manipulate forensic artifacts.
Attacks that exploit this kind of access
The rule that runs snow_sir_evidence_manage 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_sir_evidence_manage, this is the rule to start with:
snow_sir_evidence_manage 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_sir_evidence_manage call is checked against it from then on.
Questions about snow_sir_evidence_manage
Unified tool for Security Incident Response (SIR) evidence and forensic artifact chain-of-custody on sn_si_evidence, sn_si_artifact, and sn_si_attachment. Critical for audit trails — every action records who attached/exported the evidence and when. Actions: - attach — attach a new evidence record to a SIR incident with type, description, source, and an optional sys_attachment reference - list — list evidence rows linked to an incident - get — retrieve a single evidence row with related artifact and attachment metadata - hash_verify — recompute the SHA-256 hash of a stored artifact server-side (GlideDigest) and compare to the value recorded at attach time. Used to detect tampering or storage corruption - export — return a structured manifest of all evidence for an incident, suitable for handing off to legal/IR review Use when: the agent has produced or received forensic evidence (memory dumps, PCAPs, screenshots, exported logs) tied to a SIR incident and needs to track it under chain of custody. Companion tools: snow_sir_incident_manage (incident lifecycle), snow_sir_playbook_orchestrate (playbook steps that produce the evidence). Plugin gating: requires com.snc.security_incident. A 404 on sn_si_evidence is surfaced with the required plugin name. The hash_verify action uses GlideDigest via ES5-only server-side script execution. Returns: action-specific data. attach returns the created evidence row. list returns evidence summaries with hash and attached_by. get returns the row with related artifact records. hash_verify returns the recomputed hash, the stored hash, and a verified boolean. export returns the full evidence manifest for the incident. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_sir_evidence_manage: 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_sir_evidence_manage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the snow_sir_evidence_manage 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_sir_evidence_manage. 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_sir_evidence_manage 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.
This server
Across the catalogue