AI agents call browser_heartbeat_status to retrieve information from Kali Security MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access browser_heartbeat_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_heartbeat_status:
{
"version": "1",
"default": "deny",
"tools": {
"browser_heartbeat_status": {}
}
}browser_heartbeat_status 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.
browser_heartbeat_status. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.
Register the Kali Security MCP server in PolicyLayer and add a rule for browser_heartbeat_status: 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 Security MCP. Nothing to install.
browser_heartbeat_status 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 browser_heartbeat_status 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 browser_heartbeat_status. 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.
browser_heartbeat_status is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.