Use this when the user asks
AI agents call get_extension_status 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 status information about a phone extension without modifying any data. It is a read-only query operation that provides visibility into the current state of a telephone system resource. No creation, modification, deletion, or execution of external operations occurs. The blast radius of misuse is limited to potential exposure of operational status data.
From the tool's definition Tool name 'get_extension_status' and placement among sibling tools that perform monitoring/querying operations (get_active_calls, get_call_history, get_event_logs, find_contact_by_phone, find_users).
Attacks that exploit this kind of access
Use this when the user asks. 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_extension_status: 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_extension_status 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_extension_status 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_extension_status. 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_extension_status 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 →