Live up/down + latency probe for all 5 known x402 facilitators (Coinbase CDP, x402.org public, xpay.sh, cronos-x402, faremeter). Returns per-facilitator status, response time, capabilities probe, plus ecosystem-wide health score. Free tier — agents shouldn't hardcode a single facilitator; this le...
Part of the Onyx Mcp server.
Free to start. No card required.
AI agents call onyx_facilitator_health to retrieve information from Onyx Mcp without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though onyx_facilitator_health only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"onyx_facilitator_health": {}
}
}See the full Onyx Mcp policy for all 67 tools.
These attack patterns abuse exactly the kind of access onyx_facilitator_health gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Live up/down + latency probe for all 5 known x402 facilitators (Coinbase CDP, x402.org public, xpay.sh, cronos-x402, faremeter). Returns per-facilitator status, response time, capabilities probe, plus ecosystem-wide health score. Free tier — agents shouldn't hardcode a single facilitator; this lets them pick a live one. (price: $0 USDC, tier: free). It is categorised as a Read tool in the Onyx Mcp MCP Server, which means it retrieves data without modifying state.
Register the Onyx MCP server in PolicyLayer and add a rule for onyx_facilitator_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 Onyx Mcp. Nothing to install.
onyx_facilitator_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 onyx_facilitator_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 onyx_facilitator_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.
onyx_facilitator_health is provided by the Onyx MCP server (https://onyx-actions.onrender.com/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 67 Onyx Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.