Low Risk

crowdsec_decisions

Active decisions (bans currently enforced by any bouncer listening on the LAPI).

How to control crowdsec_decisions ↓

What crowdsec_decisions does on Crow

AI agents call crowdsec_decisions 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.

Low Risk

Why crowdsec_decisions needs a policy

This tool retrieves information about active security decisions/bans without modifying them. It is a query operation (Read category). Severity is high because the data returned could reveal sensitive security posture information that, if leaked to an attacker, could help them understand defensive measures and identify which IPs are blocked, potentially compromising security operations.

From the tool's definition Tool name 'crowdsec_decisions' combined with description 'Active decisions (bans currently enforced by any bouncer listening on the LAPI)' indicates this retrieves and queries the current state of security decisions—specifically, which IP addresses or…

Documented attack patterns abuse exactly the kind of access crowdsec_decisions gives an agent:

How to control crowdsec_decisions

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_decisions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crowdsec_decisions": {}
  }
}

crowdsec_decisions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crowdsec_decisions

What does the crowdsec_decisions tool do? +

Active decisions (bans currently enforced by any bouncer listening on the LAPI). 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_decisions? +

Register the Crow MCP server in PolicyLayer and add a rule for crowdsec_decisions: 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_decisions? +

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

Can I rate-limit crowdsec_decisions? +

Yes. Add a rate_limit block to the crowdsec_decisions 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_decisions completely? +

Set action: deny in the PolicyLayer policy for crowdsec_decisions. 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_decisions? +

crowdsec_decisions 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.

Enforce policy on every Crow tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.