This record as markdown: /tools/creativelead-unclick/ip-batch.md
What ip_batch does on UnClick
AI agents call ip_batch to retrieve information from UnClick 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 | — | Array of IP address strings |
api_key | string | — |
Parameters from the server's own tool schema.
Why ip_batch is rated Low
IP geolocation lookup is a straightforward read operation that queries external databases for publicly available geographic information tied to IP addresses. It retrieves data without reversible or irreversible modifications, code execution, or financial impact. The batch processing capability does not elevate the risk category — it remains a read-only lookup operation.
From the tool's definition Tool performs 'Batch IP address geolocation lookup' — a retrieval/query operation that returns location data associated with IP addresses without modifying, executing code, or causing side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs ip_batch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ip_batch, this is the rule to start with:
ip_batch 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 UnClick, apply this rule, and every ip_batch call is checked against it from then on.
Questions about ip_batch
Batch IP address geolocation lookup. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ip_batch accepts 2 parameters: ips, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for ip_batch: 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 UnClick. Nothing to install.
ip_batch 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_batch 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_batch. 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_batch is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue