oe_health

Millisecond-fast local check of the relay pipeline (daemon + browser extension) — no OpenEvidence network call.

SERVER: SOURCEhtlin222/openevidence-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/htlin222-openevidence-mcp/oe-health.md

WHAT IT DOES

What oe_health does on :

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

RISK

Why oe_health is rated Low

Even though oe_health only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs oe_health safely

PolicyLayer is an MCP gateway: it sits between your AI agents and :, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For oe_health, this is the rule to start with:

oe_health Allowed

oe_health 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": {
    "oe_health": {}
  }
}

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

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

FAQ

Questions about oe_health

What does the oe_health tool do? +

Millisecond-fast local check of the relay pipeline (daemon + browser extension) — no OpenEvidence network call. It is categorised as a Read tool in the : MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on oe_health? +

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

What risk level is oe_health? +

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

Can I rate-limit oe_health? +

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

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

oe_health is provided by the : MCP server (htlin222/openevidence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on :, and thousands of servers like it.

This server

All 19 : tools →

Across the catalogue

The MCP Attack Database →

Guides

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