Check health and response times of up to 10 service URLs in parallel. Free preview: GET https://microservice-health-check.apimesh.xyz/preview?url=... checks 1 service for free
AI agents call microservice_health_check to retrieve information from APIMesh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring/observability data about external services (health status and performance metrics). It does not create, modify, execute, or delete anything; it only reads and reports on the state of remote services. Even though the server supports financial payment mechanisms, this specific tool itself performs no financial transactions.
From the tool's definition Tool performs health checks and measures response times of service URLs without modifying, executing, or deleting any data. The description explicitly states it 'checks' services and measures response times—pure queries with no side effects.
Attacks that exploit this kind of access
Check health and response times of up to 10 service URLs in parallel. Free preview: GET https://microservice-health-check.apimesh.xyz/preview?url=... checks 1 service for free. It is categorised as a Read tool in the APIMesh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the APIMesh MCP Server MCP server in PolicyLayer and add a rule for microservice_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 APIMesh MCP Server. Nothing to install.
microservice_health_check 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 microservice_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.
Set action: deny in the PolicyLayer policy for microservice_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.
microservice_health_check is provided by the APIMesh MCP Server MCP server (mbeato/apimesh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →