Make a phone call (SIM card 1 only)
AI agents invoke call_phone to trigger actions in AutoBot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — initiating a real phone call on the device. It is not merely writing data; it causes an active telecommunication event with real-world consequences (charges, unwanted contact, privacy violations). While it could have financial implications (call charges), the primary classification is Execute since it triggers an external operation.
From the tool's definition Make a phone call (SIM card 1 only)
Attacks that exploit this kind of access
Make a phone call (SIM card 1 only). It is categorised as a Execute tool in the AutoBot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AutoBot MCP server in PolicyLayer and add a rule for call_phone: 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 AutoBot MCP. Nothing to install.
call_phone is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_phone 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 call_phone. 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.
call_phone is provided by the AutoBot MCP server (yz0903/autobot-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 →