Per-vault risk profile for tokenized real-world-asset (RWA) positions on Base (tokenized treasuries, private credit, RWA vaults like Midas). Returns two on-chain risk dimensions: (1) admin/freeze risk - whether a holder can be frozen or blacklisted or the contract upgraded, and by whom; (2) exit-...
AI agents call rwa_risk to retrieve information from Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
vault | string | — | |
protocol | string | — |
Parameters from the server's own tool schema.
This is a financial-domain analytics tool that retrieves and reports risk metrics for tokenized assets. Although the domain is financial (crypto/RWA positions), the tool itself only reads on-chain data and does not execute trades, move capital, or commit financial obligations.
From the tool's definition Tool description states it 'Returns two on-chain risk dimensions' and 'Call before allocating capital' — these are passive data retrieval operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Per-vault risk profile for tokenized real-world-asset (RWA) positions on Base (tokenized treasuries, private credit, RWA vaults like Midas). Returns two on-chain risk dimensions: (1) admin/freeze risk - whether a holder can be frozen or blacklisted or the contract upgraded, and by whom; (2) exit-liquidity - whether the position can be sold on the secondary market and at what slippage. Plus supply and TVL context. Call before allocating capital into an RWA vault. Pass vault=<id> such as midas-mtbill, or protocol=<name> such as midas. Scope: on-chain admin and liquidity risk only; not default probability, yield source, or legal terms. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
rwa_risk accepts 2 parameters: vault, protocol. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for rwa_risk: 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 Mcp Server. Nothing to install.
rwa_risk 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 rwa_risk 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 rwa_risk. 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.
rwa_risk is provided by the Mcp Server MCP server (Homie4570/lso-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
rwa_risk is one line of Mcp Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →