AI agents call rtp_streams to retrieve information from SharkMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
RTP streams analysis in packet capture context is a read operation that retrieves and presents information about Real-time Transport Protocol streams from PCAP files. The sibling tools all perform passive inspection without side effects. While the empty description lowers confidence slightly, the operational context and naming strongly indicate data retrieval only.
From the tool's definition Tool named 'rtp_streams' with empty description; context indicates it operates within Wireshark's sharkd packet analysis interface alongside sibling tools like 'conversations', 'io_stats', and 'extract_fields' which are all read-only inspection operations.
Documented attack patterns abuse exactly the kind of access rtp_streams gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SharkMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for rtp_streams:
{
"version": "1",
"default": "deny",
"tools": {
"rtp_streams": {}
}
}rtp_streams 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.
rtp_streams. It is categorised as a Read tool in the SharkMCP MCP Server, which means it retrieves data without modifying state.
Register the Shark MCP server in PolicyLayer and add a rule for rtp_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 SharkMCP. Nothing to install.
rtp_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 rtp_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 rtp_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.
rtp_streams is provided by the Shark MCP server (weirdmachine64/sharkmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 SharkMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 SharkMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.