AI agents call rpki_aspa_changes to retrieve information from Net without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, confidence is reduced. However, the name pattern ('_changes' suffix on RPKI-related tools) and server context (data retrieval focused) suggest this tool queries ASPA records rather than modifying them. This is consistent with other sibling tools (bgp_historical_lookup, bgp_leaks) that are read-only analytics. The 'changes' noun refers to what is being retrieved, not what the tool does.
From the tool's definition Tool name 'rpki_aspa_changes' contains 'changes' but lacks a description. Based on context, ASPA (Autonomous System Provider Authorization) records are part of RPKI (Resource Public Key Infrastructure).
Attacks that exploit this kind of access
rpki_aspa_changes. It is categorised as a Read tool in the Net MCP Server, which means it retrieves data without modifying state.
Register the Net MCP server in PolicyLayer and add a rule for rpki_aspa_changes: 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 Net. Nothing to install.
rpki_aspa_changes 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 rpki_aspa_changes 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 rpki_aspa_changes. 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.
rpki_aspa_changes is provided by the Net MCP server (steelcutoatmeal/net-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →