Check if Perplexica API is healthy and accessible.
AI agents call health_check to retrieve information from Perplexica MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Health checks are diagnostic read operations that query system status without modifying data or triggering external actions. The tool merely verifies API availability and health metrics, making it a low-risk Read operation. Low severity because any misuse (e.g., repeated checks) would only result in harmless status queries.
From the tool's definition Tool name is 'health_check' and description states it checks 'if Perplexica API is healthy and accessible' — a pure status query with no side effects, data retrieval, modification, or external state changes.
Documented attack patterns abuse exactly the kind of access health_check gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Perplexica MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for health_check:
{
"version": "1",
"default": "deny",
"tools": {
"health_check": {}
}
}health_check 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 if Perplexica API is healthy and accessible. It is categorised as a Read tool in the Perplexica MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Perplexica MCP Server MCP server in PolicyLayer and add a rule for 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 Perplexica MCP Server. Nothing to install.
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 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 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.
health_check is provided by the Perplexica MCP Server MCP server (tianmu/perplexica-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Perplexica MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Perplexica MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.