AI agents call peeringdb_facility 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.
This tool performs a read-only search/lookup operation against a public database. It retrieves informational data about data center facilities with no modification, deletion, or execution of code. The blast radius is minimal—an AI agent using this tool could only retrieve facility information, which is already publicly available. There are no side effects, irreversible actions, or financial implications.
From the tool's definition The tool description states 'Search for data center facilities in PeeringDB' — a query operation that retrieves public facility data from PeeringDB (a public database of internet exchange points, data centers, and network participants).
Attacks that exploit this kind of access
Search for data center facilities in PeeringDB. 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 peeringdb_facility: 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.
peeringdb_facility 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 peeringdb_facility 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 peeringdb_facility. 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.
peeringdb_facility 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 →