security.ipqs.ip_check
Check any IP address for fraud signals — proxy, VPN, Tor, bot, crawler detection with fraud score (0-100). Returns geolocation (country, city, ISP, ASN), abuse velocity, connection type, and 9+ risk indicators. Essential for e-commerce fraud prevention (IPQualityScore)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/security.ipqs.ip-check.md
What security.ipqs.ip_check does on Apibase
AI agents call security.ipqs.ip_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 |
|---|---|---|---|
ip | string | Yes | IPv4 or IPv6 address to check (e.g. "8.8.8.8", "2001:4860:4860::8888") |
strictness | integer | — | Detection strictness 0-3 (0=least strict, 3=most aggressive). Higher catches more fraud but may flag legitimate users |
allow_public_access_points | boolean | — | Allow public WiFi/library IPs to pass without penalty (default false) |
Parameters from the server's own tool schema.
Why security.ipqs.ip_check is rated Low
Queries external IP reputation service; returns data only, no side effects or actions triggered.
From the tool's definition Check IP address for fraud signals, geolocation, risk indicators — no modification or execution.
Attacks that exploit this kind of access
The rule that runs security.ipqs.ip_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.ip_check, this is the rule to start with:
security.ipqs.ip_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.ip_check call is checked against it from then on.
Questions about security.ipqs.ip_check
Check any IP address for fraud signals — proxy, VPN, Tor, bot, crawler detection with fraud score (0-100). Returns geolocation (country, city, ISP, ASN), abuse velocity, connection type, and 9+ risk indicators. Essential for e-commerce fraud prevention (IPQualityScore). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
security.ipqs.ip_check accepts 3 parameters: ip, strictness, allow_public_access_points. Required: ip. 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.ip_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.ip_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.ip_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.ip_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.ip_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