network_get_log
Get the network request log for the current page.
This record as markdown: /tools/mcp-anything/network-get-log.md
What network_get_log does on Mcp Anything
AI agents call network_get_log to retrieve information from Mcp Anything without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why network_get_log is rated Low
This tool retrieves historical network traffic data from the current page. While it is non-destructive and does not modify state, it could expose sensitive information such as API endpoints, headers, request parameters, credentials, or other PII that may be visible in network logs.
From the tool's definition Tool name is 'network_get_log' and description states 'Get the network request log for the current page' — the verb 'get' and action of retrieving logs indicates a read operation with no side effects.
Attacks that exploit this kind of access
The rule that runs network_get_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For network_get_log, this is the rule to start with:
network_get_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every network_get_log call is checked against it from then on.
Questions about network_get_log
Get the network request log for the current page. It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for network_get_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 Mcp Anything. Nothing to install.
network_get_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 network_get_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 network_get_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.
network_get_log is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue