check_frigate

Check Frigate NVR (network video recorder) health via GET /api/stats. Returns camera count, detection FPS, process load, and detector (GPU/CPU) stats. Default port 5000.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/check-frigate.md

WHAT IT DOES

What check_frigate does on Mcp Nettools

AI agents call check_frigate to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_frigate is rated Low

This tool queries a network video recorder's API to retrieve diagnostic statistics. It is a read-only operation that retrieves system health and status information from an existing service. The low severity reflects that exposure of NVR stats poses minimal risk—it reveals operational metrics but not sensitive footage or authentication credentials, and causes no system changes.

From the tool's definition Tool performs a GET request to /api/stats endpoint to retrieve health metrics (camera count, detection FPS, process load, detector stats). No modification, deletion, execution of commands, or financial operations occur.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_frigate safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_frigate, this is the rule to start with:

check_frigate Allowed

check_frigate 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": {
    "check_frigate": {}
  }
}

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

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

FAQ

Questions about check_frigate

What does the check_frigate tool do? +

Check Frigate NVR (network video recorder) health via GET /api/stats. Returns camera count, detection FPS, process load, and detector (GPU/CPU) stats. Default port 5000. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_frigate? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_frigate: 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 Mcp Nettools. Nothing to install.

What risk level is check_frigate? +

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

Can I rate-limit check_frigate? +

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

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

check_frigate is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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