crowdsec_status
LAPI reachability, active decisions (bans in force), and alert counts
This record as markdown: /tools/kh0pper-crow/crowdsec-status.md
What crowdsec_status does on Crow
AI agents call crowdsec_status to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crowdsec_status is rated Low
The tool retrieves and reports on system status metrics (API reachability, decision counts, alert counts) without modifying any data, executing code, or triggering external operations. This is purely informational and falls clearly into the Read category. The low severity reflects that misuse would only expose operational metrics rather than cause damage or access sensitive user data.
From the tool's definition Tool provides status information: 'LAPI reachability, active decisions (bans in force), and alert counts'. These are read-only queries of monitoring/security state data with no side effects.
Attacks that exploit this kind of access
The rule that runs crowdsec_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crowdsec_status, this is the rule to start with:
crowdsec_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crowdsec_status call is checked against it from then on.
Questions about crowdsec_status
LAPI reachability, active decisions (bans in force), and alert counts. 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_status: 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_status 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_status 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_status. 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_status 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue