Low Risk

mtrkr_wallet_tokens

Discover all ERC-20 tokens held by a wallet on MegaETH with balances and USD pricing. Uses hybrid discovery (token list multicall + RPC transfer log scanning) so newly received tokens are found even if not on the default token list.

Part of the Mtrkr server.

mtrkr_wallet_tokens is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MTRKR →

Free to start. No card required.

AI agents call mtrkr_wallet_tokens to retrieve information from Mtrkr without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though mtrkr_wallet_tokens only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mtrkr_wallet_tokens": {}
  }
}

See the full Mtrkr policy for all 11 tools.

Get this rule live on your own Mtrkr server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MTRKR →

View all 11 tools →

These attack patterns abuse exactly the kind of access mtrkr_wallet_tokens gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so mtrkr_wallet_tokens only ever does what you allow.

SECURE MTRKR →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the mtrkr_wallet_tokens tool do? +

Discover all ERC-20 tokens held by a wallet on MegaETH with balances and USD pricing. Uses hybrid discovery (token list multicall + RPC transfer log scanning) so newly received tokens are found even if not on the default token list.. It is categorised as a Read tool in the Mtrkr MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mtrkr_wallet_tokens? +

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

What risk level is mtrkr_wallet_tokens? +

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

Can I rate-limit mtrkr_wallet_tokens? +

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

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

mtrkr_wallet_tokens is provided by the Mtrkr MCP server (mtrkr-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mtrkr tool call.

Deterministic rules across all 11 Mtrkr tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.