AI agents call list_streams to retrieve information from Packmate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix universally denotes retrieval of a collection without modification. In a network traffic analyzer, listing streams would enumerate existing traffic streams for examination. No side effects, destructive actions, code execution, or financial operations are implied. The empty description lowers confidence slightly, but the naming pattern and server context are clear.
From the tool's definition Tool name 'list_streams' combined with sibling tools context (get_packets, get_stream, pattern_lookback, list_patterns, list_services) indicates a query/list operation on network traffic data.
Attacks that exploit this kind of access
list_streams. It is categorised as a Read tool in the Packmate MCP Server, which means it retrieves data without modifying state.
Register the Packmate MCP server in PolicyLayer and add a rule for list_streams: 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 Packmate. Nothing to install.
list_streams 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 list_streams 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 list_streams. 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.
list_streams is provided by the Packmate MCP server (umbra2728/packmate-mcp). 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 →