ip.intelligence.bulk
Look up multiple IP addresses in one call (max 100) — country, city, VPN/Tor/proxy flags, ASN, and organization for each IP (ipapi.is)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ip.intelligence.bulk.md
What ip.intelligence.bulk does on Apibase
AI agents call ip.intelligence.bulk 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 |
|---|---|---|---|
ips | array | Yes | Array of IPv4/IPv6 addresses to look up in bulk (max 100 per request) |
Parameters from the server's own tool schema.
Why ip.intelligence.bulk is rated Low
Retrieves IP geolocation and metadata; no data modification or side effects.
From the tool's definition Look up multiple IP addresses, country, city, VPN/Tor/proxy flags, ASN, organization
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ip.intelligence.bulk 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 ip.intelligence.bulk, this is the rule to start with:
ip.intelligence.bulk 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 ip.intelligence.bulk call is checked against it from then on.
Questions about ip.intelligence.bulk
Look up multiple IP addresses in one call (max 100) — country, city, VPN/Tor/proxy flags, ASN, and organization for each IP (ipapi.is). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ip.intelligence.bulk accepts 1 parameter: ips. Required: ips. 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 ip.intelligence.bulk: 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.
ip.intelligence.bulk 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 ip.intelligence.bulk 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 ip.intelligence.bulk. 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.
ip.intelligence.bulk 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