crow_frigate_latest_by_label

Most recent Frigate event for a label, across all cameras (unless a camera is given).

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/crow-frigate-latest-by-label.md

What crow_frigate_latest_by_label does on Crow

AI agents call crow_frigate_latest_by_label 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_latest_by_label is rated Low

The tool queries and retrieves event data from Frigate (a video surveillance system) based on label and optional camera filters. This is a pure read operation with no capability to modify, delete, or execute actions. The blast radius is minimal — exposure would allow an AI to access surveillance event history but not alter systems or trigger actions.

From the tool's definition Tool retrieves 'most recent Frigate event for a label' — a query operation that fetches historical event data without modification or side effects.

Questions about crow_frigate_latest_by_label

What does the crow_frigate_latest_by_label tool do? +

Most recent Frigate event for a label, across all cameras (unless a camera is given). 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 crow_frigate_latest_by_label? +

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

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

Can I rate-limit crow_frigate_latest_by_label? +

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

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

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

Across the catalogue

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