Recent CrowdSec alerts. Each alert represents one detected attack pattern (triggered scenario).
AI agents call crowdsec_alerts to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only tool that queries and retrieves security alert information. While it does not create, modify, or delete data, the high severity reflects that alert data could reveal security vulnerabilities, attack patterns, and system weaknesses if exposed to an adversary.
From the tool's definition Tool retrieves 'Recent CrowdSec alerts' representing 'detected attack patterns' - a query operation that surfaces security detection data without modifying it.
Documented attack patterns abuse exactly the kind of access crowdsec_alerts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crowdsec_alerts:
{
"version": "1",
"default": "deny",
"tools": {
"crowdsec_alerts": {}
}
}crowdsec_alerts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Recent CrowdSec alerts. Each alert represents one detected attack pattern (triggered scenario). It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crowdsec_alerts: 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 Crow. Nothing to install.
crowdsec_alerts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crowdsec_alerts 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 crowdsec_alerts. 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.
crowdsec_alerts is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.