ripe_network_info
Get network information for an IP or prefix from RIPE NCC.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ripe-network-info.md
What ripe_network_info does on UnClick
AI agents call ripe_network_info 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 |
|---|---|---|---|
resource | string | Yes | IP address or prefix. |
Parameters from the server's own tool schema.
Why ripe_network_info is rated Low
This tool queries publicly available network information from RIPE NCC (a regional internet registry). It retrieves data about IP allocations and network prefixes without creating, modifying, deleting, or executing anything.
From the tool's definition Tool description states 'Get network information for an IP or prefix from RIPE NCC' – a retrieval/query operation with no modification, deletion, or execution capability mentioned.
Attacks that exploit this kind of access
The rule that runs ripe_network_info 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 ripe_network_info, this is the rule to start with:
ripe_network_info 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 ripe_network_info call is checked against it from then on.
Questions about ripe_network_info
Get network information for an IP or prefix from RIPE NCC. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ripe_network_info accepts 1 parameter: resource. Required: resource. 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 ripe_network_info: 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.
ripe_network_info 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 ripe_network_info 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 ripe_network_info. 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.
ripe_network_info 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue