wavexis_network_requests
List network requests since page load with pagination.
This record as markdown: /tools/wavexis-mcp/wavexis-network-requests.md
What wavexis_network_requests does on Wavexis
AI agents call wavexis_network_requests to retrieve information from Wavexis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wavexis_network_requests is rated Low
This tool retrieves historical network request data for inspection purposes. It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. The 'list' and 'pagination' semantics confirm it is a read-only query operation. Severity is low because misuse would expose only monitoring/debugging data already captured by the browser.
From the tool's definition Tool name 'wavexis_network_requests' and description 'List network requests since page load with pagination' — a retrieval operation that queries browser network activity without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs wavexis_network_requests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_network_requests, this is the rule to start with:
wavexis_network_requests 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 Wavexis, apply this rule, and every wavexis_network_requests call is checked against it from then on.
Questions about wavexis_network_requests
List network requests since page load with pagination. It is categorised as a Read tool in the Wavexis MCP Server, which means it retrieves data without modifying state.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_network_requests: 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 Wavexis. Nothing to install.
wavexis_network_requests 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 wavexis_network_requests 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 wavexis_network_requests. 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.
wavexis_network_requests is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wavexis, and thousands of servers like it.
This server
Across the catalogue