check_linkding

Check Linkding bookmark manager health via GET /health. Returns healthy/reachable status. Default port 9090.

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-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.

Questions about check_linkding

What does the check_linkding tool do? +

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.

How do I enforce a policy on check_linkding? +

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.

What risk level is check_linkding? +

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

Can I rate-limit check_linkding? +

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.

How do I block check_linkding completely? +

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.

What MCP server provides check_linkding? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Nettools's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.