AI agents call extract_iocs to retrieve information from SIFTGuard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static text analysis to identify and extract forensic indicators (IPs, domains, hashes, URLs, registry keys, file paths). It reads data, performs pattern matching, and returns results. No code execution, data modification, deletion, or financial operations occur. While used in an incident response context, the tool itself is purely Read-category.
From the tool's definition Tool description states it 'Extract[s] Indicators of Compromise (IOCs) from text' — a parsing/querying operation that analyzes and retrieves data patterns from input without modifying, executing, or destroying anything.
Attacks that exploit this kind of access
Extract Indicators of Compromise (IOCs) from text: IPs, domains, file hashes, URLs, registry keys, file paths. It is categorised as a Read tool in the SIFTGuard MCP Server, which means it retrieves data without modifying state.
Register the SIFTGuard MCP server in PolicyLayer and add a rule for extract_iocs: 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 SIFTGuard. Nothing to install.
extract_iocs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the extract_iocs 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 extract_iocs. 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.
extract_iocs is provided by the SIFTGuard MCP server (sodiq-code/siftguard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →