snow_sir_indicator_manage

Unified tool for the Indicator of Compromise (IOC) lifecycle on sn_ti_observable, sn_ti_indicator, and the SIR observable join table. Manages persistent IOC records — distinct from snow_analyze_threat_intelligence, which only correlates a single IOC against feeds without persisting state. Actions...

Server Serac serac-labs/serac
Category Write
Risk class Medium
Parameters 00 required

What snow_sir_indicator_manage does on Serac

AI agents use snow_sir_indicator_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_indicator_manage needs a policy

The tool primarily creates and modifies security indicator records and incident relationships. While it deals with sensitive security data (indicators of compromise), the operations are reversible (records can be deleted or delinked, state can be changed back). This is Write rather than Execute (no code/command execution) or Destructive (no permanent deletion).

From the tool's definition The tool performs create_ioc (creates new IOC records), link_to_incident (creates join table entries), and mark_active (modifies IOC state).

Questions about snow_sir_indicator_manage

What does the snow_sir_indicator_manage tool do? +

Unified tool for the Indicator of Compromise (IOC) lifecycle on sn_ti_observable, sn_ti_indicator, and the SIR observable join table. Manages persistent IOC records — distinct from snow_analyze_threat_intelligence, which only correlates a single IOC against feeds without persisting state. Actions: - create_ioc — create a new IOC record (value, type, finding required) on sn_ti_observable - list_iocs — list IOCs, optionally filtered by type, state, source, or seen-since - link_to_incident — link an existing IOC to a SIR incident via the observable-incident join table - mark_active — mark an IOC active (re-open after resolution) - mark_resolved — mark an IOC resolved (closed, no longer interesting) - search_by_value — find IOCs by exact or fragment match on value (IP, domain, hash, URL, email) Use when: the agent needs to manage persistent IOC records — open a new IOC after triage, attach existing IOCs to a new incident, search for prior sightings of a value, or close out an IOC after eradication. Companion tools: snow_analyze_threat_intelligence (one-shot feed correlation), snow_sir_incident_manage (parent incident lifecycle), snow_sir_evidence_manage (evidence chain of custody). Table-name volatility: the IOC table name varies by SN release (sn_ti_observable / sn_ti_indicator / sn_si_observable). This tool defaults to sn_ti_observable and falls back to sn_si_observable if the primary table is absent. Plugin gating: requires either Threat Intelligence or the Security Incident Response plugin (com.snc.security_incident). A 404 on both fallback tables is surfaced with the required plugin name. Returns: action-specific data. create_ioc returns the created record. list_iocs / search_by_value return arrays of IOCs with value, type, state, source, last_seen. link_to_incident returns the join-row sys_id. mark_active / mark_resolved return the updated record. 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.

How do I enforce a policy on snow_sir_indicator_manage? +

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

What risk level is snow_sir_indicator_manage? +

snow_sir_indicator_manage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit snow_sir_indicator_manage? +

Yes. Add a rate_limit block to the snow_sir_indicator_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.

How do I block snow_sir_indicator_manage completely? +

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

What MCP server provides snow_sir_indicator_manage? +

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

// THE FULL RECORD

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