verify_token
Source verification status for a token. There is no standalone verification endpoint — this reads the launch record's published verification fields. Verdicts are queued | retrying | exact_match | needs_attention | unavailable. There is no 'partial match'. No API key required.
This record as markdown: /tools/aabxtract-programmable-mcp-server/verify-token.md
What verify_token does on Programmable
AI agents call verify_token to retrieve information from Programmable 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 |
|---|---|---|---|
address | string | Yes | Token contract address to verify. |
chainId | integer | — | Chain to query. Defaults to 4663 (Robinhood Chain). Use 1 for Ethereum Mainnet. |
Parameters from the server's own tool schema.
Why verify_token is rated Low
Even though verify_token only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs verify_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Programmable, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_token, this is the rule to start with:
verify_token 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 Programmable, apply this rule, and every verify_token call is checked against it from then on.
Questions about verify_token
Source verification status for a token. There is no standalone verification endpoint — this reads the launch record's published verification fields. Verdicts are queued | retrying | exact_match | needs_attention | unavailable. There is no 'partial match'. No API key required. It is categorised as a Read tool in the Programmable MCP Server, which means it retrieves data without modifying state.
verify_token accepts 2 parameters: address, chainId. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the Programmable MCP server in PolicyLayer and add a rule for verify_token: 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 Programmable. Nothing to install.
verify_token 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 verify_token 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 verify_token. 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.
verify_token is provided by the Programmable MCP server (@aabxtract/programmable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Programmable, and thousands of servers like it.
This server
Across the catalogue