near_token_safety
Who can change a NEAR token's contract? GO / HOLD / STOP — Before an agent takes a NEP-141 token on NEAR: who can change it? Counts full-access keys that can redeploy the contract, and asks the contract for an owner and a pause switch — issued tokens like USDt keep control through owner methods, not keys. No key and no owner → GO; key- or owner-controlled → HOLD; paused, no contract or not NEP-141 → STOP. Plus name, symbol, supply, and NEAR Intents liquidity and price. Live from the NEAR RPC. Required input: token. Priced $0.02 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"token": "<token>"
},
"name": "near_token_safety"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | NEAR token contract account |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | The result payload. Shape is service-specific; every field is documented in the tool description. | |
| service | No | The service id that answered. | |
| checkedAt | No | ISO-8601 timestamp of when the underlying reads were taken. |