Get list of all RWA token issuers with aggregated TVL, token counts, and average APY. Sorted by TVL.
AI agents call get_issuers to retrieve information from RWA Pipe MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward data retrieval operation—fetching a list of token issuers with computed aggregate statistics. There are no side effects, no state changes, no code execution, and no financial transactions. It is a passive query against blockchain/asset data.
From the tool's definition Tool retrieves and lists RWA token issuers with aggregated metrics (TVL, token counts, average APY). The verbs 'Get' and 'list' and the description 'retrieves...
Attacks that exploit this kind of access
Get list of all RWA token issuers with aggregated TVL, token counts, and average APY. Sorted by TVL. It is categorised as a Read tool in the RWA Pipe MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RWA Pipe MCP Server MCP server in PolicyLayer and add a rule for get_issuers: 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 RWA Pipe MCP Server. Nothing to install.
get_issuers 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_issuers 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_issuers. 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_issuers is provided by the RWA Pipe MCP Server MCP server (rwapipe/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 →