List Frigate detection events with optional filters. Cached for 30s at the HTTP layer so chatty polling does not drive Frigate to 100% CPU.
AI agents call crow_frigate_list_events 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 tool retrieves and queries detection event data from Frigate (a video surveillance/object detection system) without creating, modifying, or deleting any data. The caching mechanism and mention of 'polling' confirm this is a read operation designed for safe, repeated queries.
From the tool's definition Tool performs a 'List' operation to retrieve Frigate detection events with optional filters. The description explicitly states it lists events and includes caching to prevent resource exhaustion, indicating read-only data retrieval with no modification or…
Documented attack patterns abuse exactly the kind of access crow_frigate_list_events 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 crow_frigate_list_events:
{
"version": "1",
"default": "deny",
"tools": {
"crow_frigate_list_events": {}
}
} crow_frigate_list_events 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.
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.
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.