crow_frigate_list_cameras

List all configured Frigate cameras with detect/record state, resolution, and tracked objects. Reads /api/config.

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-list-cameras.md

WHAT IT DOES

What crow_frigate_list_cameras does on Crow

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

RISK

Why crow_frigate_list_cameras is rated Low

This tool retrieves camera configuration and status information from a Frigate API endpoint without creating, modifying, deleting, or executing any operations. It is a pure read operation that queries existing data.

From the tool's definition Tool description explicitly states "List all configured Frigate cameras" and "Reads /api/config". The verb "List" and "Reads" indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_frigate_list_cameras 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_cameras, this is the rule to start with:

crow_frigate_list_cameras Allowed

crow_frigate_list_cameras is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crow_frigate_list_cameras": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_frigate_list_cameras call is checked against it from then on.

FAQ

Questions about crow_frigate_list_cameras

What does the crow_frigate_list_cameras tool do? +

List all configured Frigate cameras with detect/record state, resolution, and tracked objects. Reads /api/config. 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_list_cameras? +

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

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

Can I rate-limit crow_frigate_list_cameras? +

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

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

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

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →