check_invidious
Check Invidious YouTube frontend reachability via GET /api/v1/stats. Returns software version when healthy. Default port 3000.
This record as markdown: /tools/aaronckj-mcp-nettools/check-invidious.md
What check_invidious does on Mcp Nettools
AI agents call check_invidious 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.
Why check_invidious is rated Low
This tool queries the status of an Invidious instance and retrieves version information. It has no side effects on the target system—it only reads data via a GET request. There is no capability to modify, delete, or execute code on the target system. Even if an agent misuses this tool by checking arbitrary instances, the blast radius is minimal as it only probes reachability and reads public-facing API responses.
From the tool's definition Tool performs a GET request to check reachability and retrieve software version information via '/api/v1/stats'. The GET method is inherently read-only and retrieves system information without modification.
Attacks that exploit this kind of access
The rule that runs check_invidious 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_invidious, this is the rule to start with:
check_invidious 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 Mcp Nettools, apply this rule, and every check_invidious call is checked against it from then on.
Questions about check_invidious
Check Invidious YouTube frontend reachability via GET /api/v1/stats. Returns software version when healthy. Default port 3000. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_invidious: 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.
check_invidious 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 check_invidious 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 check_invidious. 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.
check_invidious 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.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue