Low Risk

subscribe_threats

Open a named, stateful subscription to live threat push delivery. Returns a subscription_id. Pass it to drain_subscription() to collect the IOCs that have arrived since your last drain — zero polling, each caller gets their own isolated stream. Multiple subscribers receive independent copies of e...

Risk signalsBulk/mass operation — affects multiple targets

Part of the Nullcone Threat Intelligence server.

subscribe_threats is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE NULLCONE THREAT INTELLIGENCE →

Free to start. No card required.

AI agents call subscribe_threats to retrieve information from Nullcone Threat Intelligence 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 subscribe_threats 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "subscribe_threats": {}
  }
}

See the full Nullcone Threat Intelligence policy for all 30 tools.

Get this rule live on your own Nullcone Threat Intelligence server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NULLCONE THREAT INTELLIGENCE →

View all 30 tools →

These attack patterns abuse exactly the kind of access subscribe_threats gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so subscribe_threats only ever does what you allow.

SECURE NULLCONE THREAT INTELLIGENCE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the subscribe_threats tool do? +

Open a named, stateful subscription to live threat push delivery. Returns a subscription_id. Pass it to drain_subscription() to collect the IOCs that have arrived since your last drain — zero polling, each caller gets their own isolated stream. Multiple subscribers receive independent copies of every matching IOC. Subscriptions expire after 1 hour of inactivity (no drain calls). Composition filters let you narrow the stream: - ioc_types: only deliver these IOC types (empty = all) - families: only deliver IOCs from these malware families (empty = all) - tags: only deliver IOCs with at least one of these tags (empty = all) Requires the MCP server to be running in SSE mode (MCP_TRANSPORT=sse) with a live SpacetimeDB push subscription active. Args: min_severity: Minimum severity to deliver (0-10). Default 5 (medium+). ioc_types: List of IOC types to include. E.g. ["skill","prompt","ip"]. Valid: hash_md5, hash_sha1, hash_sha256, ip, ip_port, domain, url, yara, email, mutex, filepath, asn, ja3, imphash, cve, prompt, skill. Empty = all types. families: List of malware family names to include. Empty = all. tags: List of tags — IOC must match at least one. Empty = all. Returns: subscription_id: Opaque ID — pass to drain_subscription() / unsubscribe() push_active: Whether the background push subscription is running filters: Echo of the composition filters applied. It is categorised as a Read tool in the Nullcone Threat Intelligence MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on subscribe_threats? +

Register the Nullcone Threat Intelligence MCP server in PolicyLayer and add a rule for subscribe_threats: 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 Nullcone Threat Intelligence. Nothing to install.

What risk level is subscribe_threats? +

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

Can I rate-limit subscribe_threats? +

Yes. Add a rate_limit block to the subscribe_threats 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 subscribe_threats completely? +

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

subscribe_threats is provided by the Nullcone Threat Intelligence MCP server (https://nullcone.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nullcone Threat Intelligence tool call.

Deterministic rules across all 30 Nullcone Threat Intelligence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.