Low Risk

threat_intel

Check domain against abuse.ch URLhaus for known malware-distribution URLs (single source — for multi-feed correlation use ioc_lookup which adds ThreatFox and, for IPs, Feodo Tracker). Use for fast domain-level threat assessment; use phishing_check for specific URLs. Free: 30/hr, Pro: 500/hr. Retu...

Part of the ContrastAPI MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call threat_intel to retrieve information from ContrastAPI without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though threat_intel only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

contrastcyber-contrastapi.yaml
tools:
  threat_intel:
    rules:
      - action: allow

See the full ContrastAPI policy for all 53 tools.

Tool Name threat_intel
Category Read
Risk Level Low

View all 53 tools →

Agents calling read-class tools like threat_intel have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the threat_intel tool do? +

Check domain against abuse.ch URLhaus for known malware-distribution URLs (single source — for multi-feed correlation use ioc_lookup which adds ThreatFox and, for IPs, Feodo Tracker). Use for fast domain-level threat assessment; use phishing_check for specific URLs. Free: 30/hr, Pro: 500/hr. Returns {malware_urls, threat_tags, threat_status, summary}.. It is categorised as a Read tool in the ContrastAPI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on threat_intel? +

Add a rule in your Intercept YAML policy under the tools section for threat_intel. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ContrastAPI MCP server.

What risk level is threat_intel? +

threat_intel is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit threat_intel? +

Yes. Add a rate_limit block to the threat_intel rule in your Intercept 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 threat_intel completely? +

Set action: deny in the Intercept policy for threat_intel. 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 threat_intel? +

threat_intel is provided by the ContrastAPI MCP server (contrastcyber/contrastapi). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.