check_hoarder
Check Hoarder bookmarks manager reachability via GET /api/v1/health. Default port 3000.
This record as markdown: /tools/aaronckj-mcp-nettools/check-hoarder.md
What check_hoarder does on Mcp Nettools
AI agents call check_hoarder 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_hoarder is rated Low
This tool queries the health status of a service endpoint. It is a passive health check that only retrieves status information without modifying, deleting, executing operations, or committing financial transactions. The action is a simple GET request to a standard health endpoint, which is a read operation with minimal blast radius if misused.
From the tool's definition Tool performs a GET request to a health endpoint (/api/v1/health) to check reachability of Hoarder bookmarks manager. GET requests are read operations that retrieve data without side effects.
Attacks that exploit this kind of access
The rule that runs check_hoarder 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_hoarder, this is the rule to start with:
check_hoarder 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_hoarder call is checked against it from then on.
Questions about check_hoarder
Check Hoarder bookmarks manager reachability via GET /api/v1/health. 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_hoarder: 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_hoarder 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_hoarder 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_hoarder. 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_hoarder 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