singularityagent__inspect_exit

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--inspect-exit.md

WHAT IT DOES

What singularityagent__inspect_exit does on Rokha

AI agents call singularityagent__inspect_exit 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.

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

Parameters from the server's own tool schema.

RISK

Why singularityagent__inspect_exit is rated Low

Queries Solana token metadata to identify exit restrictions; purely informational analysis with no transaction or state changes.

From the tool's definition inspect, find out, names mechanisms, without side effects

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs singularityagent__inspect_exit 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__inspect_exit, this is the rule to start with:

singularityagent__inspect_exit Allowed

singularityagent__inspect_exit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "singularityagent__inspect_exit": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every singularityagent__inspect_exit call is checked against it from then on.

FAQ

Questions about singularityagent__inspect_exit

What does the singularityagent__inspect_exit tool do? +

Before buying a Solana token, find out what could stop you selling it. Names the specific mechanisms rather than scoring the token: a transfer hook (issuer code runs on every transfer, including your sale, and can refuse it), a permanent delegate (an address can move the token out of your wallet without you signing), a live freeze authority (your token account can be frozen, leaving a balance you own and cannot sell), a default-frozen account state, a non-transferable mint, transfer fees, and supply concentrated in one non-pool account. Each entry says who holds the power. canExit is false when at least one mechanism can block a sale or seize the balance. canExit: true does not mean safe to buy — this reads the mint account and the largest holders, not the market, so it says nothing about whether liquidity is locked, how deep the pool is, or what the token is worth. Read completeness, which always says what was not covered. This is a read: it builds nothing, signs nothing, and routes no trade. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does singularityagent__inspect_exit accept? +

singularityagent__inspect_exit 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__inspect_exit? +

Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__inspect_exit: 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__inspect_exit? +

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

Can I rate-limit singularityagent__inspect_exit? +

Yes. Add a rate_limit block to the singularityagent__inspect_exit 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__inspect_exit completely? +

Set action: deny in the PolicyLayer policy for singularityagent__inspect_exit. 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__inspect_exit? +

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

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

binary_inspect on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →