crypto.token-safety

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/crypto.token-safety.md

WHAT IT DOES

What crypto.token-safety does on Mcp

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

RISK

Why crypto.token-safety is rated Low

This tool queries and retrieves token metadata and risk indicators from GoPlus; it does not execute trades, transfer funds, approve tokens, or perform any on-chain transactions. It is a passive information-gathering tool for pre-trade analysis. Although the server context involves crypto and financial instruments, the tool itself only performs Read operations (data retrieval).

From the tool's definition Tool returns risk screening data: honeypot flag, buy/sell tax, token properties (open-source/proxy/mintable), holder concentration, blacklist/whitelist flags.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crypto.token-safety safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto.token-safety, this is the rule to start with:

crypto.token-safety Allowed

crypto.token-safety 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": {
    "crypto.token-safety": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every crypto.token-safety call is checked against it from then on.

FAQ

Questions about crypto.token-safety

What does the crypto.token-safety tool do? +

Token honeypot & rug-pull risk screen (via GoPlus, free/keyless). For an ERC-20 on any EVM chain, returns honeypot flag, buy/sell tax, open-source/proxy/mintable status, hidden-owner / take-back-ownership / selfdestruct / external-call risks, blacklist/whitelist/anti-whale flags, holder count, and owner/creator concentration. Essential pre-trade safety check. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crypto.token-safety? +

Register the MCP server in PolicyLayer and add a rule for crypto.token-safety: 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 Mcp. Nothing to install.

What risk level is crypto.token-safety? +

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

Can I rate-limit crypto.token-safety? +

Yes. Add a rate_limit block to the crypto.token-safety 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 crypto.token-safety completely? +

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

crypto.token-safety is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

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