phone.twilio.lookup
Validate and look up phone number info — format validation, country, national format. Optional: carrier name, line type (mobile/landline/VoIP), caller name CNAM (Twilio)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/phone.twilio.lookup.md
What phone.twilio.lookup does on Apibase
AI agents call phone.twilio.lookup to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
phone_number | string | Yes | Phone number in E.164 format (e.g. "+14157012311", "+442071234567") |
include_carrier | boolean | — | Include carrier/line type info (costs extra credit). Returns carrier name, line type (mobile/landline/voip). |
include_caller_name | boolean | — | Include caller name CNAM lookup (costs extra credit). US numbers only. |
Parameters from the server's own tool schema.
Why phone.twilio.lookup is rated Low
Tool queries phone metadata without modifying data or executing external actions.
From the tool's definition Validate and look up phone number info — format validation, country, national format
Attacks that exploit this kind of access
The rule that runs phone.twilio.lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For phone.twilio.lookup, this is the rule to start with:
phone.twilio.lookup 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 Apibase, apply this rule, and every phone.twilio.lookup call is checked against it from then on.
Questions about phone.twilio.lookup
Validate and look up phone number info — format validation, country, national format. Optional: carrier name, line type (mobile/landline/VoIP), caller name CNAM (Twilio). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
phone.twilio.lookup accepts 3 parameters: phone_number, include_carrier, include_caller_name. Required: phone_number. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for phone.twilio.lookup: 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 Apibase. Nothing to install.
phone.twilio.lookup 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 phone.twilio.lookup 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 phone.twilio.lookup. 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.
phone.twilio.lookup is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue