oe_health
Millisecond-fast local check of the relay pipeline (daemon + browser extension) — no OpenEvidence network call.
This record as markdown: /tools/htlin222-openevidence-mcp/oe-health.md
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.
Why oe_health is rated Low
This is a health/status check operation that queries the state of local components (daemon and browser extension). It has no side effects, makes no network calls, and does not create, modify, delete, or execute anything. It is purely diagnostic and informational, making it a Read category tool with low severity.
From the tool's definition Tool performs a 'local check' of the relay pipeline with 'no OpenEvidence network call', indicating it only retrieves status information without modifying or executing external operations.
Attacks that exploit this kind of access
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 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 :, apply this rule, and every oe_health call is checked against it from then on.
Questions about oe_health
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.
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.
oe_health 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 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.
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.
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.
More on :, and thousands of servers like it.
This server
Across the catalogue