New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

singularityagent__mint_audit

What a Solana mint account permits, read from the mint itself: which token program owns it, whether more can be minted, whether holder accounts can be frozen, whether its name can still be rewritten, and every Token-2022 extension on it — permanent delegate, transfer hook, transfer fee, default-f...

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/singularityagent--mint-audit.md

What singularityagent__mint_audit does on Rokha

AI agents call singularityagent__mint_audit to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
mint string Yes The mint address.
chain string — Solana chain id or alias. Defaults to "solana"; a non-Solana chain is refused.

Parameters from the server's own tool schema.

Why singularityagent__mint_audit is rated Low

Reads on-chain Solana mint account data; no state changes, but reveals sensitive token permissions.

From the tool's definition read from the mint itself, returns powers and addresses

Risk signalsBulk/mass operation — affects multiple targets

Questions about singularityagent__mint_audit

What does the singularityagent__mint_audit tool do? +

What a Solana mint account permits, read from the mint itself: which token program owns it, whether more can be minted, whether holder accounts can be frozen, whether its name can still be rewritten, and every Token-2022 extension on it — permanent delegate, transfer hook, transfer fee, default-frozen accounts, non-transferable, interest-bearing. Reach for it whenever someone asks whether a token is safe, what a mint can do to them, or why a transfer failed, and before treating an unfamiliar mint as ordinary. It returns powers and the addresses holding them, plus what is permanently settled — never a score or a verdict, because liquidity, holder concentration and the deployer are not in these bytes. Solana only. The metadata link is reported and deliberately never fetched. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does singularityagent__mint_audit accept? +

singularityagent__mint_audit accepts 2 parameters: mint, chain. Required: mint. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on singularityagent__mint_audit? +

Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__mint_audit: 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.

What risk level is singularityagent__mint_audit? +

singularityagent__mint_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit singularityagent__mint_audit? +

Yes. Add a rate_limit block to the singularityagent__mint_audit 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.

How do I block singularityagent__mint_audit completely? +

Set action: deny in the PolicyLayer policy for singularityagent__mint_audit. 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.

What MCP server provides singularityagent__mint_audit? +

singularityagent__mint_audit 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Rokha's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.