singularityagent__token_identity
Read what a Solana mint says it is — its name, ticker, metadata link — and, crucially, whether any of that can be rewritten later at the same address. Where the update authority is revoked and the link is content-addressed (an IPFS CID), what the mint declares is fixed at mint time and cannot be ...
This record as markdown: /tools/ai-rokha-rokha/singularityagent--token-identity.md
What singularityagent__token_identity does on Rokha
AI agents use singularityagent__token_identity to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mint | string | Yes | Mint address, or an address-book alias for one. |
chain | string | — | Solana chain id or alias. Defaults to "solana". |
fetch | boolean | — | Also fetch the metadata document and read the accounts it declares. Off by default: it is an outbound request to a URL the deployer chose. |
Parameters from the server's own tool schema.
Why singularityagent__token_identity is rated Medium
An AI agent can call singularityagent__token_identity faster than any human can review: one bad instruction and it creates or modifies resources in Rokha by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs singularityagent__token_identity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For singularityagent__token_identity, this is the rule to start with:
singularityagent__token_identity stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every singularityagent__token_identity call is checked against it from then on.
Questions about singularityagent__token_identity
Read what a Solana mint says it is — its name, ticker, metadata link — and, crucially, whether any of that can be rewritten later at the same address. Where the update authority is revoked and the link is content-addressed (an IPFS CID), what the mint declares is fixed at mint time and cannot be swapped. Set fetch to also read the document and return the accounts it declares (X, Telegram, website, GitHub); it is off by default because the link is a URL chosen by whoever deployed the mint. Use it to answer whether a token, or an account claiming to represent one, is the real one — the answer is always the mint address, never the ticker. A mint wearing a curated token’s symbol or name at a different address is reported as impersonation. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
singularityagent__token_identity accepts 3 parameters: mint, chain, fetch. Required: mint. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__token_identity: 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 Rokha. Nothing to install.
singularityagent__token_identity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the singularityagent__token_identity 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 singularityagent__token_identity. 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.
singularityagent__token_identity is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue