api_pera_asset_verification_status
Get the verification status of an Algorand mainnet asset from Pera Wallet. Returns verification tier (verified, trusted, suspicious, unverified) and explorer URL.
This record as markdown: /tools/goplausible-algorand-mcp/api-pera-asset-verification-status.md
What api_pera_asset_verification_status does on Algorand MCP
AI agents call api_pera_asset_verification_status to retrieve information from Algorand MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why api_pera_asset_verification_status is rated Low
This tool queries blockchain data (asset verification status from Pera Wallet) without modifying, deleting, or executing any operations. It is purely informational and read-only. The sibling tools on this server include order creation, cancellation, and claiming operations (Execute/Financial/Destructive), but this specific tool performs only a lookup.
From the tool's definition Tool description indicates it 'Get[s] the verification status' and 'Returns verification tier and explorer URL' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs api_pera_asset_verification_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Algorand MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For api_pera_asset_verification_status, this is the rule to start with:
api_pera_asset_verification_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Algorand MCP, apply this rule, and every api_pera_asset_verification_status call is checked against it from then on.
Questions about api_pera_asset_verification_status
Get the verification status of an Algorand mainnet asset from Pera Wallet. Returns verification tier (verified, trusted, suspicious, unverified) and explorer URL. It is categorised as a Read tool in the Algorand MCP MCP Server, which means it retrieves data without modifying state.
Register the Algorand MCP server in PolicyLayer and add a rule for api_pera_asset_verification_status: 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 Algorand MCP. Nothing to install.
api_pera_asset_verification_status 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 api_pera_asset_verification_status 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 api_pera_asset_verification_status. 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.
api_pera_asset_verification_status is provided by the Algorand MCP server (goplausible/algorand-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Algorand, and thousands of servers like it.
This server
Across the catalogue