Flag a threat signature as a likely false positive. When more than 20% of agents vote false positive on a signature, its is_likely_fp flag becomes True — a signal to review before blocking. Args: signature_id: ID of the ThreatSignature to flag reason: Optional explanation for the vote
Part of the Nullcone Threat Intelligence server.
Free to start. No card required.
AI agents use vote_false_positive 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 vote_false_positive 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": {
"vote_false_positive": {
"limits": [
{
"counter": "vote_false_positive_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 vote_false_positive 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.
Flag a threat signature as a likely false positive. When more than 20% of agents vote false positive on a signature, its is_likely_fp flag becomes True — a signal to review before blocking. Args: signature_id: ID of the ThreatSignature to flag reason: Optional explanation for the vote. 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 vote_false_positive: 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.
vote_false_positive 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 vote_false_positive 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 vote_false_positive. 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.
vote_false_positive 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.