check_tubearchivist
Check TubeArchivist (YouTube archiver) health via GET /api/ping/. Returns healthy status and version info. Default port 8000.
This record as markdown: /tools/aaronckj-mcp-nettools/check-tubearchivist.md
What check_tubearchivist does on Mcp Nettools
AI agents call check_tubearchivist 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_tubearchivist is rated Low
This tool performs a health check on a TubeArchivist service by making a GET request to its ping API endpoint. It retrieves status and version information without modifying, deleting, or executing operations on the target system. The GET HTTP method and ping semantics confirm this is a read-only diagnostic operation with minimal blast radius if misused.
From the tool's definition Tool description explicitly states 'Check TubeArchivist health via GET /api/ping/' and 'Returns healthy status and version info'. GET requests are read-only; ping endpoints have no side effects.
Attacks that exploit this kind of access
The rule that runs check_tubearchivist 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_tubearchivist, this is the rule to start with:
check_tubearchivist 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_tubearchivist call is checked against it from then on.
Questions about check_tubearchivist
Check TubeArchivist (YouTube archiver) health via GET /api/ping/. Returns healthy status and version info. Default port 8000. 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_tubearchivist: 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_tubearchivist 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_tubearchivist 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_tubearchivist. 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_tubearchivist 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