Check connectivity and health of configured APIs
AI agents call check_api_health to retrieve information from Mcp Api Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic check of API connectivity and health status. It retrieves information about system state without creating, modifying, or deleting data, and has no side effects. This is a read-only operation. Severity is low because misuse would only expose non-sensitive operational status information.
From the tool's definition check_api_health uses 'Check connectivity and health' language, which describes querying/monitoring status without modifying any state. This is analogous to a GET request or health probe endpoint.
Documented attack patterns abuse exactly the kind of access check_api_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Api Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for check_api_health:
{
"version": "1",
"default": "deny",
"tools": {
"check_api_health": {}
}
}check_api_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check connectivity and health of configured APIs. It is categorised as a Read tool in the Mcp Api Gateway MCP Server, which means it retrieves data without modifying state.
Register the Mcp Api Gateway MCP server in PolicyLayer and add a rule for check_api_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 Mcp Api Gateway. Nothing to install.
check_api_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 check_api_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 check_api_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.
check_api_health is provided by the Mcp Api Gateway MCP server (rflpazini/mcp-api-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Mcp Api Gateway tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Mcp Api Gateway tools catalogued and risk-classified — across an index of 42,500+ MCP servers.