get_network_capture
AI agents call get_network_capture to retrieve information from WebControl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves previously captured network data (likely from configure_network_capture). Retrieving network logs is a read-only operation with no side effects—data is not modified or deleted. While it could expose sensitive information in headers or payloads, the action itself is passive data retrieval, fitting the Read category.
From the tool's definition Tool name 'get_network_capture' indicates retrieval of network traffic data. Empty description limits certainty, but the 'get_' prefix and context within a browser automation server suggest this queries/retrieves captured network information without modifying…
Attacks that exploit this kind of access
get_network_capture. It is categorised as a Read tool in the WebControl MCP Server, which means it retrieves data without modifying state.
Register the WebControl MCP server in PolicyLayer and add a rule for get_network_capture: 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 WebControl. Nothing to install.
get_network_capture 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 get_network_capture 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 get_network_capture. 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.
get_network_capture is provided by the WebControl MCP server (matansht/webcontrol). 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 →