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

Agent View of the PolicyLayer registry record for `singularityagent__mint_audit`. HTML page: https://policylayer.com/tools/ai-rokha-rokha/singularityagent--mint-audit

## Facts

- Tool: `singularityagent__mint_audit`
- Server: Rokha (`https://rokha.ai/mcp/jsonrpc`) — https://policylayer.com/tools/ai-rokha-rokha.md
- Homepage: https://github.com/aetherBytes/rokha-sdk
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `mint` | string | yes | The mint address. |
| `chain` | string | no | Solana chain id or alias. Defaults to "solana"; a non-Solana chain is refused. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "singularityagent__mint_audit",
    "arguments": {
      "mint": "<mint>"
    }
  }
}
```

## 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 own definition: "read from the mint itself, returns powers and addresses"

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Rokha:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "singularityagent__mint_audit": {}
  }
}
```

## Other tools on Rokha (215)

- `adspace_bid_cancel` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/adspace-bid-cancel.md
- `delete_harness` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/delete-harness.md
- `hook_delete` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/hook-delete.md
- `rig_node_remove` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/rig-node-remove.md
- `schedule_delete` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/schedule-delete.md
- `signet_paper_reset` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/signet-paper-reset.md
- `signet_revoke` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/signet-revoke.md
- `auth_wallet_verify` — Execute — https://policylayer.com/tools/ai-rokha-rokha/auth-wallet-verify.md
- `harness_author` — Execute — https://policylayer.com/tools/ai-rokha-rokha/harness-author.md
- `orbitx__orbitx_gc_focus` — Execute — https://policylayer.com/tools/ai-rokha-rokha/orbitx--orbitx-gc-focus.md
- `registry_adopt` — Execute — https://policylayer.com/tools/ai-rokha-rokha/registry-adopt.md
- `registry_list_server` — Execute — https://policylayer.com/tools/ai-rokha-rokha/registry-list-server.md
- `rig_author` — Execute — https://policylayer.com/tools/ai-rokha-rokha/rig-author.md
- `rig_run` — Execute — https://policylayer.com/tools/ai-rokha-rokha/rig-run.md
- `sandbox_exec` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-exec.md
- `sandbox_start` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-start.md
- `sandbox_stop` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-stop.md
- `send_agent_message` — Execute — https://policylayer.com/tools/ai-rokha-rokha/send-agent-message.md
- `signet_approve` — Execute — https://policylayer.com/tools/ai-rokha-rokha/signet-approve.md
- `singularityagent__mesh` — Execute — https://policylayer.com/tools/ai-rokha-rokha/singularityagent--mesh.md
- `studio_doors` — Execute — https://policylayer.com/tools/ai-rokha-rokha/studio-doors.md
- `x_link_start` — Execute — https://policylayer.com/tools/ai-rokha-rokha/x-link-start.md
- `adnet_feed` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adnet-feed.md
- `adnet_join` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adnet-join.md
- `ads_order` — Financial — https://policylayer.com/tools/ai-rokha-rokha/ads-order.md
- `adspace_bid` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adspace-bid.md
- `auth_wallet_challenge` — Financial — https://policylayer.com/tools/ai-rokha-rokha/auth-wallet-challenge.md
- `campaign_claim` — Financial — https://policylayer.com/tools/ai-rokha-rokha/campaign-claim.md
- `carry_order` — Financial — https://policylayer.com/tools/ai-rokha-rokha/carry-order.md
- `creator_earnings` — Financial — https://policylayer.com/tools/ai-rokha-rokha/creator-earnings.md
- …and 185 more: https://policylayer.com/tools/ai-rokha-rokha.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ai-rokha-rokha · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-rokha-rokha