AI agents call get_protocol_addresses to retrieve information from Usdd Test without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches static or semi-static protocol configuration data (addresses, market parameters). It has no capability to modify state, execute transactions, move funds, or trigger external operations. The fallback-to-cache behavior confirms it is a safe read operation.
From the tool's definition "Get Chainlog-backed protocol addresses, configured ilks, and PSM markets" — purely retrieves configuration data without modification or side effects.
Attacks that exploit this kind of access
Get Chainlog-backed protocol addresses, configured ilks, and PSM markets. Uses cache when fresh and falls back to cache if live Chainlog reads fail. It is categorised as a Read tool in the Usdd Test MCP Server, which means it retrieves data without modifying state.
Register the Usdd Test MCP server in PolicyLayer and add a rule for get_protocol_addresses: 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 Usdd Test. Nothing to install.
get_protocol_addresses 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 get_protocol_addresses 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 get_protocol_addresses. 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.
get_protocol_addresses is provided by the Usdd Test MCP server (mcp-server-usdd-test). 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 →