crow_frigate_stats
Frigate system stats: version, detector inference time, CPU usage per process. Cached for 30s.
This record as markdown: /tools/kh0pper-crow/crow-frigate-stats.md
What crow_frigate_stats does on Crow
AI agents call crow_frigate_stats 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_stats is rated Low
This tool only queries and returns system monitoring data about a Frigate video detection system. It has no side effects, cannot modify state, execute commands, or affect other systems. The 30-second caching indicates it is a read-only monitoring endpoint. This is a straightforward Read category tool with low severity due to the informational nature of system statistics.
From the tool's definition Tool retrieves Frigate system statistics (version, detector inference time, CPU usage) with caching. No modification, deletion, or execution capability described. Pure data retrieval operation.
Attacks that exploit this kind of access
The rule that runs crow_frigate_stats 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_stats, this is the rule to start with:
crow_frigate_stats 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_stats call is checked against it from then on.
Questions about crow_frigate_stats
Frigate system stats: version, detector inference time, CPU usage per process. Cached for 30s. 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_stats: 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_stats 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_stats 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_stats. 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_stats 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