crow_frigate_set_detect
Enable/disable motion detection for a camera. DESTRUCTIVE: disabling detect also stops motion-triggered recording on that camera. Use sparingly.
This record as markdown: /tools/kh0pper-crow/crow-frigate-set-detect.md
What crow_frigate_set_detect does on Crow
AI agents call crow_frigate_set_detect to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crow_frigate_set_detect is rated Critical
The tool can disable motion detection which irreversibly halts motion-triggered recording on a camera. This is a security-critical, hard-to-recover-from action (missed recordings cannot be retroactively captured), making it Destructive with high severity.
From the tool's definition DESTRUCTIVE: disabling detect also stops motion-triggered recording on that camera
Attacks that exploit this kind of access
The rule that runs crow_frigate_set_detect 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_set_detect, this is the rule to start with:
crow_frigate_set_detect is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_frigate_set_detect call is checked against it from then on.
Questions about crow_frigate_set_detect
Enable/disable motion detection for a camera. DESTRUCTIVE: disabling detect also stops motion-triggered recording on that camera. Use sparingly. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_frigate_set_detect: 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_set_detect is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the crow_frigate_set_detect 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_set_detect. 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_set_detect 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