make_call
Preview or queue a call that rings the seller’s own phone first and connects the recipient once the seller answers. The Adrata API places both legs through its carrier (the provider it reports, e.g. Telnyx) from the caller ID the seller chose; use list_calling_identities to see which number that ...
This record as markdown: /tools/adrata-adrata-mcp/make-call.md
What make_call does on Adrata
AI agents call make_call to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why make_call is rated Low
Even though make_call only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs make_call safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For make_call, this is the rule to start with:
make_call is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every make_call call is checked against it from then on.
Questions about make_call
Preview or queue a call that rings the seller’s own phone first and connects the recipient once the seller answers. The Adrata API places both legs through its carrier (the provider it reports, e.g. Telnyx) from the caller ID the seller chose; use list_calling_identities to see which number that is. Requires a configured seller phone plus explicit approval, reason and a stable idempotencyKey. A queued request does not prove a connected call. Read status before retrying; never automatically replace a key after an uncertain outcome. Not for emergency calls. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.
Register the Adrata 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 Adrata. Nothing to install.
make_call 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 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 Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adrata, and thousands of servers like it.
This server
Across the catalogue