Monitor HTTP requests, responses, and network timing. Perfect for API debugging and performance analysis.
AI agents call debug_network_activity to retrieve information from Firefox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool monitors and reads network activity (HTTP requests, responses, timing) without modifying or executing anything. However, it can capture sensitive data like API keys, tokens, or private data transmitted over the network, giving it a medium severity rating despite being read-only.
From the tool's definition Monitor HTTP requests, responses, and network timing. Perfect for API debugging and performance analysis.
Documented attack patterns abuse exactly the kind of access debug_network_activity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Firefox MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_network_activity:
{
"version": "1",
"default": "deny",
"tools": {
"debug_network_activity": {}
}
} debug_network_activity 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.
Monitor HTTP requests, responses, and network timing. Perfect for API debugging and performance analysis. It is categorised as a Read tool in the Firefox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firefox MCP Server MCP server in PolicyLayer and add a rule for debug_network_activity: 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 Firefox MCP Server. Nothing to install.
debug_network_activity 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 debug_network_activity 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 debug_network_activity. 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.
debug_network_activity is provided by the Firefox MCP Server MCP server (jediluke/firefox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Firefox MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Firefox MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.