Check the health status of the Kali API server.
AI agents call server_health to retrieve information from Kali Linux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple health check that queries the state of the server and returns status information. It has no side effects, does not execute code or commands, does not modify data, and does not perform destructive operations. Despite being on a Kali Linux penetration testing server, this specific tool is purely informational and diagnostic in nature, making it a Read category risk with low severity.
From the tool's definition Tool name 'server_health' and description 'Check the health status of the Kali API server' indicate a monitoring/diagnostic query operation that retrieves status information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check the health status of the Kali API server. It is categorised as a Read tool in the Kali Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for server_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 Kali Linux MCP Server. Nothing to install.
server_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 server_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 server_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.
server_health is provided by the Kali Linux MCP Server MCP server (ofryma/custom-mcp-library). 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 →