browser_heartbeat_status

What browser_heartbeat_status does on Kali Security MCP

AI agents call browser_heartbeat_status to retrieve information from Kali Security MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why browser_heartbeat_status is rated Low

With an empty description, classification relies on the tool name. 'Heartbeat' and 'status' are passive monitoring terms implying a read operation that retrieves state information without side effects. Given the Kali penetration testing context, this likely monitors browser automation tool health. However, confidence is moderate due to lack of descriptive detail.

From the tool's definition Tool name 'browser_heartbeat_status' suggests monitoring or querying the status of a browser heartbeat mechanism. The 'heartbeat' pattern typically indicates health checks or status queries rather than modifications or executions.

The rule that runs browser_heartbeat_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_heartbeat_status, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_heartbeat_status": {}
  }
}

Questions about browser_heartbeat_status