crowdsec_status

LAPI reachability, active decisions (bans in force), and alert counts

SERVERCrow SOURCEkh0pper/crow
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about crowdsec_status

What does the crowdsec_status tool do? +

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.

How do I enforce a policy on crowdsec_status? +

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.

What risk level is crowdsec_status? +

crowdsec_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crowdsec_status? +

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.

How do I block crowdsec_status completely? +

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.

What MCP server provides crowdsec_status? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.