Use this when the user asks
AI agents call get_forwarding_profiles 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 forwarding profile information from the 3CX Phone System. It queries existing configuration data and has no side effects—it neither creates, modifies, deletes, nor executes actions. While the description is incomplete ('Use this when the user asks'), the name and context establish it as a data retrieval operation.
From the tool's definition Tool name 'get_forwarding_profiles' indicates retrieval of forwarding configuration data. Sibling tools like 'find_users', 'find_queues', 'get_active_calls', and 'get_call_history' are all Read operations that query system state without modification.
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_forwarding_profiles: 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_forwarding_profiles 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_forwarding_profiles 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_forwarding_profiles. 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_forwarding_profiles 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 →