Low Risk

health_check

Check if the docpull service is running and available.

How to control health_check ↓

What health_check does on Docpull

AI agents call health_check to retrieve information from Docpull without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why health_check needs a policy

This is a simple health/status check that only queries the availability of the service. It has no capability to access, modify, or affect any data or resources. It is purely informational and read-only in nature, making it the lowest risk category with minimal blast radius if misused.

From the tool's definition Tool name 'health_check' and description 'Check if the docpull service is running and available' indicate a status check operation with no data retrieval, modification, or side effects.

Documented attack patterns abuse exactly the kind of access health_check gives an agent:

How to control health_check

PolicyLayer is an MCP gateway — it sits between your AI agents and Docpull, and nothing reaches the server without passing your rules. This is the rule we recommend for health_check:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "health_check": {}
  }
}

health_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Docpull — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about health_check

What does the health_check tool do? +

Check if the docpull service is running and available. It is categorised as a Read tool in the Docpull MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on health_check? +

Register the Docpull MCP server in PolicyLayer and add a rule for health_check: 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 Docpull. Nothing to install.

What risk level is health_check? +

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

Can I rate-limit health_check? +

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

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

health_check is provided by the Docpull MCP server (jesse-dxju/docpull). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docpull tool call.

Start from Docpull, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

3 Docpull tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.