check_linkding
Check Linkding bookmark manager health via GET /health. Returns healthy/reachable status. Default port 9090.
This record as markdown: /tools/aaronckj-mcp-nettools/check-linkding.md
What check_linkding does on Mcp Nettools
AI agents call check_linkding 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_linkding is rated Low
This tool performs a health check by making a GET request to a standard health endpoint. It retrieves status information about the Linkding service without modifying any data or triggering external actions. This is a pure read operation with minimal blast radius if misused—at worst, it could be used for reconnaissance of internal services, but poses no direct risk to data integrity or system state.
From the tool's definition Tool description states it 'Check[s] Linkding bookmark manager health via GET /health' and 'Returns healthy/reachable status'. GET request and health check endpoint are read-only operations with no side effects.
Attacks that exploit this kind of access
The rule that runs check_linkding 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_linkding, this is the rule to start with:
check_linkding 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_linkding call is checked against it from then on.
Questions about check_linkding
Check Linkding bookmark manager health via GET /health. Returns healthy/reachable status. Default port 9090. 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_linkding: 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_linkding 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_linkding 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_linkding. 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_linkding 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