security.ipqs.phone_check
Check phone number for fraud risk — detects VOIP, prepaid, risky numbers, carrier info, line type (mobile/landline/VOIP), active status, leaked data. Returns fraud score (0-100) and geographic location. Supports international numbers with country filter (IPQualityScore)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/security.ipqs.phone-check.md
What security.ipqs.phone_check does on Apibase
AI agents call security.ipqs.phone_check 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 | string | Yes | Phone number to check in E.164 or national format (e.g. "+12125551234", "2125551234") |
country | string | — | ISO 2-letter country code for national format numbers (e.g. "US", "GB") |
strictness | integer | — | Fraud detection strictness 0-2 |
Parameters from the server's own tool schema.
Why security.ipqs.phone_check is rated Low
Retrieves phone metadata and fraud risk scoring; no side effects or data modification.
From the tool's definition Check phone number, detects VOIP, prepaid, risky numbers, carrier info, returns fraud score.
Attacks that exploit this kind of access
The rule that runs security.ipqs.phone_check 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 security.ipqs.phone_check, this is the rule to start with:
security.ipqs.phone_check 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 security.ipqs.phone_check call is checked against it from then on.
Questions about security.ipqs.phone_check
Check phone number for fraud risk — detects VOIP, prepaid, risky numbers, carrier info, line type (mobile/landline/VOIP), active status, leaked data. Returns fraud score (0-100) and geographic location. Supports international numbers with country filter (IPQualityScore). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
security.ipqs.phone_check accepts 3 parameters: phone, country, strictness. Required: phone. 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 security.ipqs.phone_check: 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.
security.ipqs.phone_check 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 security.ipqs.phone_check 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 security.ipqs.phone_check. 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.
security.ipqs.phone_check 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