AI agents use threat_mitigate to create or update resources in Novyx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Novyx environment.
This tool updates the status of a threat signature record to 'mitigated', which is a reversible state change (Write). It modifies data in the governance/audit system but does not delete records or execute code. Severity is medium because incorrectly marking a threat as mitigated could suppress active security alerts, but the action appears to be a status update that can be corrected.
From the tool's definition "Mark a threat signature as mitigated"
Documented attack patterns abuse exactly the kind of access threat_mitigate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Novyx, and nothing reaches the server without passing your rules. This is the rule we recommend for threat_mitigate:
{
"version": "1",
"default": "deny",
"tools": {
"threat_mitigate": {
"limits": [
{
"counter": "threat_mitigate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}threat_mitigate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Mark a threat signature as mitigated. It is categorised as a Write tool in the Novyx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Novyx MCP server in PolicyLayer and add a rule for threat_mitigate: 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 Novyx. Nothing to install.
threat_mitigate 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 threat_mitigate 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 threat_mitigate. 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.
threat_mitigate is provided by the Novyx MCP server (novyxlabs/novyx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 120 Novyx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
120 Novyx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.