crow_frigate_list_events
List Frigate detection events with optional filters. Cached for 30s at the HTTP layer so chatty polling does not drive Frigate to 100% CPU.
This record as markdown: /tools/kh0pper-crow/crow-frigate-list-events.md
What crow_frigate_list_events does on Crow
AI agents call crow_frigate_list_events 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 crow_frigate_list_events is rated Low
This tool retrieves detection events from Frigate (a video/object detection system) with optional filters. It performs no data modification, deletion, or execution—just querying. The caching detail reinforces that it's a non-destructive read operation. Severity is low because listing events has minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states: 'List Frigate detection events with optional filters.' The verb 'List' indicates a read-only retrieval operation. The note about caching and polling suggests this is for querying/monitoring purposes without modifying underlying data.
Attacks that exploit this kind of access
The rule that runs crow_frigate_list_events 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 crow_frigate_list_events, this is the rule to start with:
crow_frigate_list_events 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 crow_frigate_list_events call is checked against it from then on.
Questions about crow_frigate_list_events
List Frigate detection events with optional filters. Cached for 30s at the HTTP layer so chatty polling does not drive Frigate to 100% CPU. 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 crow_frigate_list_events: 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.
crow_frigate_list_events 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 crow_frigate_list_events 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 crow_frigate_list_events. 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.
crow_frigate_list_events 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