AI agents call get_jst_buyback_stats 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 retrieves and queries financial statistics from existing treasury report data. It performs no modifications, deletions, or external operations—it simply fetches and returns information. While the data relates to financial protocol metrics, the tool itself only reads/queries without moving money, creating obligations, or executing state-changing operations. Classification as Read is appropriate.
From the tool's definition Tool name includes 'get_' prefix and description states 'Get JST buyback/burn statistics from treasury report data', indicating pure data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
Get JST buyback/burn statistics from treasury report data (mainnet data). 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_jst_buyback_stats: 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_jst_buyback_stats 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_jst_buyback_stats 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_jst_buyback_stats. 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_jst_buyback_stats 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 →