check_hedgedoc

Check HedgeDoc collaborative markdown notes server health via GET /api/v2/status. Returns version and connection count. Default port 3000.

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

WHAT IT DOES

What check_hedgedoc does on Mcp Nettools

AI agents call check_hedgedoc 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.

RISK

Why check_hedgedoc is rated Low

This tool performs a read-only health check on a HedgeDoc server by querying a status endpoint. It retrieves server version and connection count information without modifying, executing, or deleting anything. This is a straightforward diagnostic read operation with minimal blast radius—even if misused by an AI agent, it only gathers publicly available server metadata.

From the tool's definition Tool description states it "Check[s] HedgeDoc collaborative markdown notes server health via GET /api/v2/status" and "Returns version and connection count." The GET method and read-only nature of status/health checks confirm retrieval without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_hedgedoc 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_hedgedoc, this is the rule to start with:

check_hedgedoc Allowed

check_hedgedoc is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_hedgedoc": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_hedgedoc call is checked against it from then on.

FAQ

Questions about check_hedgedoc

What does the check_hedgedoc tool do? +

Check HedgeDoc collaborative markdown notes server health via GET /api/v2/status. Returns version and connection count. Default port 3000. 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_hedgedoc? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_hedgedoc: 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_hedgedoc? +

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

Can I rate-limit check_hedgedoc? +

Yes. Add a rate_limit block to the check_hedgedoc 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_hedgedoc completely? +

Set action: deny in the PolicyLayer policy for check_hedgedoc. 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_hedgedoc? +

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

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →