Place an outbound voice call. Twilio fetches TwiML from
AI agents invoke make_call to trigger actions in Mcp Afip. 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.
Making an outbound call is an external operation with real-world effects (consuming telephony resources, contacting recipients). It is not a simple data read or write — it executes an action through an external service (Twilio/TwiML). Misuse could result in unwanted calls, harassment, or cost incurrence, making severity high.
From the tool's definition 'Place an outbound voice call' — triggers an external real-world telephony operation via Twilio
Documented attack patterns abuse exactly the kind of access make_call gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for make_call:
{
"version": "1",
"default": "deny",
"tools": {
"make_call": {
"limits": [
{
"counter": "make_call_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
Place an outbound voice call. Twilio fetches TwiML from. It is categorised as a Execute tool in the Mcp Afip MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for 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 Mcp Afip. Nothing to install.
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 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 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.
make_call is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.