Submit a threat indicator (IOC) to the shared intelligence network. The IOC is automatically classified into a malware family, metadata is compressed, and deduplication is handled atomically. All subscribed agents see the new IOC instantly. Args: ioc_type: IOC category. One of: hash_md5, hash_sha...
Part of the Nullcone Threat Intelligence server.
Free to start. No card required.
AI agents use submit_ioc to create or modify resources in Nullcone Threat Intelligence. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call submit_ioc repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Nullcone Threat Intelligence.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"submit_ioc": {
"limits": [
{
"counter": "submit_ioc_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Nullcone Threat Intelligence policy for all 30 tools.
These attack patterns abuse exactly the kind of access submit_ioc gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Submit a threat indicator (IOC) to the shared intelligence network. The IOC is automatically classified into a malware family, metadata is compressed, and deduplication is handled atomically. All subscribed agents see the new IOC instantly. Args: ioc_type: IOC category. One of: hash_md5, hash_sha1, hash_sha256, ip, ip_port, domain, url, yara, email, mutex, registry, filepath, asn, ja3, imphash, cve, prompt, skill value: The indicator value (e.g. "evil.example.com", "1.2.3.4") severity: 0-10. Use Severity enum values: 1=info, 3=low, 5=medium, 7=high, 9=critical confidence: 0-100 confidence score context: Free-text context about why this is malicious tags: List of tags (e.g. ["c2", "phishing", "ransomware"]) source: Origin of the intel (e.g. "honeypot", "sandbox", "osint") family_hint: Optional malware family name to skip auto-classification. It is categorised as a Write tool in the Nullcone Threat Intelligence MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nullcone Threat Intelligence MCP server in PolicyLayer and add a rule for submit_ioc: 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.
submit_ioc is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_ioc 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 submit_ioc. 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.
submit_ioc 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.
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.