Generate detection rules (Sigma, SPL, KQL) for all discovered attacks. Every offensive technique gets a corresponding detection rule for blue teams. Runs asynchronously; returns immediately with status='running'. Rules attach to findings in the engagement; pull them with get_findings(engagement_i...
AI agents use generate_detection_rules to create or update resources in Pentest Ai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pentest Ai environment.
This tool creates new detection rule artifacts within the engagement system. While the rules themselves are non-malicious (defensive in nature—'for blue teams'), the tool is performing a Write operation by generating and storing new data objects. It is not Read (data retrieval only), not Execute (does not run/trigger external operations), not Destructive (rules can be removed), and not Financial.
From the tool's definition Tool generates and attaches detection rules (Sigma, SPL, KQL) to findings in the engagement; creates new data structures (rules) that are stored and retrieved later via get_findings().
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access generate_detection_rules gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentest Ai, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_detection_rules:
{
"version": "1",
"default": "deny",
"tools": {
"generate_detection_rules": {
"limits": [
{
"counter": "generate_detection_rules_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_detection_rules 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.
Generate detection rules (Sigma, SPL, KQL) for all discovered attacks. Every offensive technique gets a corresponding detection rule for blue teams. Runs asynchronously; returns immediately with status='running'. Rules attach to findings in the engagement; pull them with get_findings(engagement_id) once status flips to 'completed'. It is categorised as a Write tool in the Pentest Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pentest Ai MCP server in PolicyLayer and add a rule for generate_detection_rules: 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 Pentest Ai. Nothing to install.
generate_detection_rules 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 generate_detection_rules 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 generate_detection_rules. 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.
generate_detection_rules is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ MCP servers.