net.rpki-validity
RPKI Route Origin Validation for a (BGP origin AS, prefix) pair — is this AS authorized to originate this prefix? Pass asn (AS15169) + prefix (8.8.8.0/24). Returns status (valid / invalid = possible hijack / unknown), a hijackSignal boolean, validating ROAs, and a description. Live RIR/RPKI data ...
This record as markdown: /tools/io-github-2s-io-mcp/net.rpki-validity.md
What net.rpki-validity does on Mcp
AI agents call net.rpki-validity to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why net.rpki-validity is rated Low
This is fundamentally a read-only security validation tool that queries public BGP/RPKI data to assess route legitimacy. It retrieves information and returns results (valid/invalid status, hijack signals, ROAs) without side effects.
From the tool's definition Tool performs RPKI Route Origin Validation — a query operation that 'checks' if an AS is authorized to originate a prefix. Returns status, ROAs, and description without modifying any data. Uses 'Live RIR/RPKI data via RIPEstat' for lookups.
Attacks that exploit this kind of access
The rule that runs net.rpki-validity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For net.rpki-validity, this is the rule to start with:
net.rpki-validity 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 Mcp, apply this rule, and every net.rpki-validity call is checked against it from then on.
Questions about net.rpki-validity
RPKI Route Origin Validation for a (BGP origin AS, prefix) pair — is this AS authorized to originate this prefix? Pass asn (AS15169) + prefix (8.8.8.0/24). Returns status (valid / invalid = possible hijack / unknown), a hijackSignal boolean, validating ROAs, and a description. Live RIR/RPKI data via RIPEstat (keyless). The core BGP-security check. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for net.rpki-validity: 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 Mcp. Nothing to install.
net.rpki-validity 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 net.rpki-validity 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 net.rpki-validity. 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.
net.rpki-validity is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue