AI agents call get_auto_attendants to retrieve information from Oitvoip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves auto attendant configurations for a domain without modifying, deleting, or executing any operations. It is a straightforward query operation consistent with other Read tools on this server (get_agents, get_domains, get_cdr_records, etc.). The blast radius of misuse is minimal—an attacker gains visibility into auto attendant settings but cannot alter system state or trigger external actions.
From the tool's definition Tool name 'get_auto_attendants' with description 'Get auto attendants for a domain' indicates a retrieval operation. The verb 'Get' and lack of any modification language confirms read-only behavior.
Attacks that exploit this kind of access
Get auto attendants for a domain. It is categorised as a Read tool in the Oitvoip MCP Server, which means it retrieves data without modifying state.
Register the Oitvoip MCP server in PolicyLayer and add a rule for get_auto_attendants: 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 Oitvoip. Nothing to install.
get_auto_attendants 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_auto_attendants 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_auto_attendants. 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_auto_attendants is provided by the Oitvoip MCP server (oitapps/oitvoip-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 →