ip_reputation
Risk profile for an IP address: geolocation and network (ASN/ISP/org) plus two abuse signals - whether it is a known Tor exit node, and whether it appears on the abuse.ch Feodo botnet command-and-control blocklist. For fraud, abuse, and security screening. Keyless.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/ip-reputation.md
What ip_reputation does on Livedatalink
AI agents call ip_reputation to retrieve information from Livedatalink 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 screen. |
Parameters from the server's own tool schema.
Why ip_reputation is rated Low
This tool queries and returns information about an IP address from public/reference databases (geolocation, ASN, Tor exit node status, botnet blocklist status). It is purely informational with no side effects. While the information could be used maliciously (e.g., reconnaissance), the tool itself only reads data.
From the tool's definition Tool description states it 'retrieves' a 'Risk profile for an IP address' with 'geolocation and network (ASN/ISP/org) plus two abuse signals'. The verbs are query-oriented (get profile data, check blocklists).
Attacks that exploit this kind of access
The rule that runs ip_reputation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ip_reputation, this is the rule to start with:
ip_reputation 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 Livedatalink, apply this rule, and every ip_reputation call is checked against it from then on.
Questions about ip_reputation
Risk profile for an IP address: geolocation and network (ASN/ISP/org) plus two abuse signals - whether it is a known Tor exit node, and whether it appears on the abuse.ch Feodo botnet command-and-control blocklist. For fraud, abuse, and security screening. Keyless. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
ip_reputation accepts 1 parameter: ip. Required: ip. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for ip_reputation: 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 Livedatalink. Nothing to install.
ip_reputation 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_reputation 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_reputation. 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_reputation is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue