Returns full configuration of a specific SIP trunk including registration details, codecs, routes, and authentication. Get the trunk Id from list_trunks first.
AI agents call get_trunk_details to retrieve information from 3CX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves trunk configuration data without modifying or deleting it, placing it in the Read category. While it is a read operation, the sensitivity of the information returned—particularly registration details and authentication information for SIP trunks—poses significant security risk if exposed to an unauthorized agent, as this data could be used for lateral attacks, credential theft, or VoIP system…
From the tool's definition Tool description states it 'Returns full configuration of a specific SIP trunk including registration details, codecs, routes, and authentication.' The verb 'Returns' indicates data retrieval with no modification.
Attacks that exploit this kind of access
Returns full configuration of a specific SIP trunk including registration details, codecs, routes, and authentication. Get the trunk Id from list_trunks first. It is categorised as a Read tool in the 3CX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 3CX MCP Server MCP server in PolicyLayer and add a rule for get_trunk_details: 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 3CX MCP Server. Nothing to install.
get_trunk_details 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 get_trunk_details 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 get_trunk_details. 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.
get_trunk_details is provided by the 3CX MCP Server MCP server (ssig-it/3cx-mcp-server). 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 →