ip_batch

Batch IP address geolocation lookup.

Server UnClick @unclick/mcp-server
Category Read
Risk class Low
Parameters 21 required

What ip_batch does on UnClick

AI agents call ip_batch to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
ips array Yes Array of IP address strings
api_key string

Parameters from the server's own tool schema.

Why ip_batch needs a policy

This tool performs batch lookups of IP address geolocation data. It retrieves information but does not create, modify, delete, or execute operations. The blast radius of misuse is limited to information disclosure—an agent might geolocate IPs without authorization, but this does not constitute Write, Execute, Destructive, or Financial harm.

From the tool's definition Tool name 'ip_batch' and description 'Batch IP address geolocation lookup' indicate a query/retrieval operation. 'Lookup' and 'geolocation' are read operations that retrieve data without modifying or executing code.

Risk signalsHandles credentials or secrets (api_key)

Questions about ip_batch

What does the ip_batch tool do? +

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.

What parameters does ip_batch accept? +

ip_batch accepts 2 parameters: ips, api_key. Required: ips. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ip_batch? +

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.

What risk level is ip_batch? +

ip_batch is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ip_batch? +

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.

How do I block ip_batch completely? +

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.

What MCP server provides ip_batch? +

ip_batch is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.