Get coin/token metadata by ID or contract address, or list popular coins
AI agents call get-coin to retrieve information from Paragraph MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only information about cryptocurrency tokens—metadata such as ID, contract address, or popularity metrics. It performs no writes, deletions, or state changes. The verb 'Get' and 'list' confirm query-only semantics. While the server context mentions financial operations (Paragraph is a publication platform), this specific tool is purely informational and poses minimal risk if misused.
From the tool's definition Tool name 'get-coin' and description 'Get coin/token metadata by ID or contract address, or list popular coins' indicate retrieval of public blockchain metadata with no modification capability.
Attacks that exploit this kind of access
Get coin/token metadata by ID or contract address, or list popular coins. It is categorised as a Read tool in the Paragraph MCP MCP Server, which means it retrieves data without modifying state.
Register the Paragraph MCP server in PolicyLayer and add a rule for get-coin: 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 Paragraph MCP. Nothing to install.
get-coin 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-coin 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-coin. 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-coin is provided by the Paragraph MCP server (paragraph-xyz/paragraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →