ripe_asn_neighbours
Get peering neighbours for an ASN from RIPE NCC.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ripe-asn-neighbours.md
What ripe_asn_neighbours does on UnClick
AI agents call ripe_asn_neighbours 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 |
|---|---|---|---|
asn | string | Yes | ASN (e.g. AS13335). |
Parameters from the server's own tool schema.
Why ripe_asn_neighbours is rated Low
This tool queries a public network registry (RIPE NCC) to retrieve peering neighbour information for a given Autonomous System Number (ASN). It performs no modifications, deletions, or external operations—only data retrieval. The information retrieved is public registry data with minimal sensitive scope. Misuse would be limited to reconnaissance or network mapping, which carries low blast radius.
From the tool's definition Tool name 'ripe_asn_neighbours' and description 'Get peering neighbours for an ASN from RIPE NCC' indicate a query/lookup operation that retrieves publicly available network peering information.
Attacks that exploit this kind of access
The rule that runs ripe_asn_neighbours 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_asn_neighbours, this is the rule to start with:
ripe_asn_neighbours 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_asn_neighbours call is checked against it from then on.
Questions about ripe_asn_neighbours
Get peering neighbours for an ASN from RIPE NCC. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ripe_asn_neighbours accepts 1 parameter: asn. Required: asn. 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_asn_neighbours: 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_asn_neighbours 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_asn_neighbours 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_asn_neighbours. 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_asn_neighbours 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