AI agents call browser_get_network_log 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.
Despite the empty description reducing confidence slightly, the naming pattern strongly indicates this tool retrieves or queries browser network logs without modifying or executing operations. It fits the 'Read' category as it fetches data with no side effects. In a penetration testing context, network logs provide reconnaissance data.
From the tool's definition Tool name 'browser_get_network_log' indicates retrieval of browser network logs. The verb 'get' and the noun 'log' (data artifact) suggest read-only querying of existing network traffic data.
Documented attack patterns abuse exactly the kind of access browser_get_network_log 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_get_network_log:
{
"version": "1",
"default": "deny",
"tools": {
"browser_get_network_log": {}
}
}browser_get_network_log 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_get_network_log. 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_get_network_log: 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_get_network_log 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_get_network_log 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_get_network_log. 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_get_network_log 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.