AI agents call reconstruct_tcap_dialogue to retrieve information from Tshark without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
TCAP dialogue reconstruction is a passive analysis operation that takes existing captured packets and reassembles their logical flow for inspection. This is analogous to other analysis tools on the same server and does not modify state, execute arbitrary code, destroy data, or move money. The absence of a description slightly reduces confidence, but the naming pattern and context strongly suggest read-only analysis.
From the tool's definition Tool name 'reconstruct_tcap_dialogue' suggests reassembling transaction-oriented signaling dialogue from existing packet data. TCAP (Transaction Capabilities Application Part) is a telecom protocol layer.
Attacks that exploit this kind of access
reconstruct_tcap_dialogue. It is categorised as a Read tool in the Tshark MCP Server, which means it retrieves data without modifying state.
Register the Tshark MCP server in PolicyLayer and add a rule for reconstruct_tcap_dialogue: 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 Tshark. Nothing to install.
reconstruct_tcap_dialogue 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 reconstruct_tcap_dialogue 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 reconstruct_tcap_dialogue. 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.
reconstruct_tcap_dialogue is provided by the Tshark MCP server (ouonet/tshark-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 →