get_token_metadata
Fetch on-chain ERC-20 metadata (symbol, name, decimals) for any token address on an EVM chain — no wallet or balance required. Also detects EIP-1967 transparent proxies and returns the current implementation address when present. Prefer this over running raw simulate_transaction calls against sym...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-token-metadata.md
What get_token_metadata does on VaultPilot MCP
AI agents call get_token_metadata to retrieve information from VaultPilot MCP 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 |
|---|---|---|---|
chain | string | — | |
address | string | Yes |
Parameters from the server's own tool schema.
Why get_token_metadata is rated Low
This tool retrieves metadata from smart contracts without modifying state, executing code, or initiating transactions. The explicit mention of detecting proxy implementation addresses and recommending its use 'over running raw simulate_transaction calls' further confirms it performs passive queries only. The capability to detect EIP-1967 proxies is still a read operation that returns existing contract information.
From the tool's definition Tool description states 'Fetch on-chain ERC-20 metadata (symbol, name, decimals)' and 'no wallet or balance required', clearly indicating read-only retrieval of publicly available blockchain data with no side effects.
Attacks that exploit this kind of access
The rule that runs get_token_metadata safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_token_metadata, this is the rule to start with:
get_token_metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every get_token_metadata call is checked against it from then on.
Questions about get_token_metadata
Fetch on-chain ERC-20 metadata (symbol, name, decimals) for any token address on an EVM chain — no wallet or balance required. Also detects EIP-1967 transparent proxies and returns the current implementation address when present. Prefer this over running raw simulate_transaction calls against symbol()/name()/decimals() selectors. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_token_metadata accepts 2 parameters: chain, address. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_token_metadata: 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 VaultPilot MCP. Nothing to install.
get_token_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_token_metadata 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.
Set action: deny in the PolicyLayer policy for get_token_metadata. 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.
get_token_metadata is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue