Retrieve enriched community context for a specific IOC by its numeric entity ID.
AI agents call ioc.context to retrieve information from OPTIX: Operational Platform for Threat Intelligence Exploration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves threat intelligence context data based on an IOC (Indicator of Compromise) identifier. The operation is non-destructive, non-modifying, and returns enriched information for analysis purposes.
From the tool's definition Tool name 'ioc.context' and description 'Retrieve enriched community context for a specific IOC' indicates a data retrieval operation with no side effects. The verb 'Retrieve' and context of querying threat intelligence feeds align with read-only operations.
Attacks that exploit this kind of access
Retrieve enriched community context for a specific IOC by its numeric entity ID. It is categorised as a Read tool in the OPTIX: Operational Platform for Threat Intelligence Exploration MCP Server, which means it retrieves data without modifying state.
Register the OPTIX: Operational Platform for Threat Intelligence Exploration MCP server in PolicyLayer and add a rule for ioc.context: 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 OPTIX: Operational Platform for Threat Intelligence Exploration. Nothing to install.
ioc.context 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 ioc.context 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 ioc.context. 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.
ioc.context is provided by the OPTIX: Operational Platform for Threat Intelligence Exploration MCP server (AdamWaldie/OPTIX-MCP). 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 →