twilio_make_call
Initiate an outbound phone call via Twilio.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/twilio-make-call.md
What twilio_make_call does on UnClick
AI agents invoke twilio_make_call to trigger actions in UnClick. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | E.164 phone number to call |
url | string | — | URL that returns TwiML for the call |
from | string | Yes | Your Twilio phone number |
twiml | string | — | TwiML instructions for the call |
auth_token | string | Yes | |
account_sid | string | Yes |
Parameters from the server's own tool schema.
Why twilio_make_call is rated High
This tool triggers a real-world external operation (placing a phone call) via the Twilio API. It is not merely reading or writing data — it executes an action with immediate real-world effects (calling a phone number). Misuse could result in harassment, spam calls, or unauthorized charges, making severity high.
From the tool's definition Initiate an outbound phone call via Twilio
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs twilio_make_call safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For twilio_make_call, this is the rule to start with:
twilio_make_call stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every twilio_make_call call is checked against it from then on.
Questions about twilio_make_call
Initiate an outbound phone call via Twilio. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
twilio_make_call accepts 6 parameters: to, url, from, twiml, auth_token, account_sid. Required: to, from, auth_token, account_sid. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for twilio_make_call: 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 UnClick. Nothing to install.
twilio_make_call 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 twilio_make_call 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 twilio_make_call. 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.
twilio_make_call is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue