trace_get_network_flow
Get a recorded request-scoped network flow from a trace.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/trace-get-network-flow.md
What trace_get_network_flow does on Jshookmcp
AI agents call trace_get_network_flow to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why trace_get_network_flow is rated Low
Retrieves network flow data from traces; no modification, but exposure of sensitive network communication details.
From the tool's definition Get a recorded request-scoped network flow from a trace.
Attacks that exploit this kind of access
The rule that runs trace_get_network_flow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trace_get_network_flow, this is the rule to start with:
trace_get_network_flow 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 Jshookmcp, apply this rule, and every trace_get_network_flow call is checked against it from then on.
Questions about trace_get_network_flow
Get a recorded request-scoped network flow from a trace. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.
Register the Jshook MCP server in PolicyLayer and add a rule for trace_get_network_flow: 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 Jshookmcp. Nothing to install.
trace_get_network_flow 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 trace_get_network_flow 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 trace_get_network_flow. 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.
trace_get_network_flow is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue