Get the Risk & Rights Score for an asset across six dimensions: - backing (0-100): proof of reserves, audit cadence, backing mechanism - enforceability (0-100): governing law, issuer verification, legal documents - control (0-100): issuer power risk — freeze, mint, burn, blacklist, upgrade - exit...
Part of the Realmint server.
Free to start. No card required.
AI agents call realmint_get_score to retrieve information from Realmint without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though realmint_get_score only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"realmint_get_score": {}
}
}See the full Realmint policy for all 7 tools.
These attack patterns abuse exactly the kind of access realmint_get_score gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get the Risk & Rights Score for an asset across six dimensions: - backing (0-100): proof of reserves, audit cadence, backing mechanism - enforceability (0-100): governing law, issuer verification, legal documents - control (0-100): issuer power risk — freeze, mint, burn, blacklist, upgrade - exit (0-100): redemption, transferability, KYC/whitelist, settlement, holding periods - liquidity (0-100): market data, venue count, evidence docs - social (0-100): Twitter activity (recency-weighted; unverified handles are penalized below the worst observed tier) Also returns a weighted composite (0-100, higher is better). Weights and penalty tiers are versioned server-side — see policy_version in the response. Combine with the asset's metadata.lifecycle field (from realmint_get_asset) to detect dead/migrated tokens — those are score-capped at 49. Suggested thresholds for decision-making: - composite ≥ 75: typical case, proceed - 55 ≤ composite < 75: elevated friction (gates, missing audits, etc.); review the asset's flags before proceeding - composite < 55: high risk; abort or require explicit user override. It is categorised as a Read tool in the Realmint MCP Server, which means it retrieves data without modifying state.
Register the Realmint MCP server in PolicyLayer and add a rule for realmint_get_score: 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 Realmint. Nothing to install.
realmint_get_score 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 realmint_get_score 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 realmint_get_score. 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.
realmint_get_score is provided by the Realmint MCP server (https://mcp.realmint.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Realmint tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.