three_price
Return the live USD price of $THREE (Jupiter primary, Birdeye fallback). Pass usd to also get how much $THREE that amount buys (token amount + atomic units). Read-only — no signer or payment required.
This record as markdown: /tools/io-github-nirholas-three-token-mcp/three-price.md
What three_price does on $THREE Token
AI agents call three_price to retrieve information from $THREE Token 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 |
|---|---|---|---|
usd | number | — | Optional USD amount to quote into $THREE. |
Parameters from the server's own tool schema.
Why three_price is rated Low
This tool retrieves pricing data from external sources (Jupiter and Birdeye) without modifying, executing, or consuming resources. It is a straightforward data retrieval endpoint with no capability to alter state, execute code, or incur financial obligations.
From the tool's definition The description explicitly states 'Read-only — no signer or payment required' and the tool returns 'the live USD price of $THREE', which is a pure query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs three_price safely
PolicyLayer is an MCP gateway: it sits between your AI agents and $THREE Token, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For three_price, this is the rule to start with:
three_price 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 $THREE Token, apply this rule, and every three_price call is checked against it from then on.
Questions about three_price
Return the live USD price of $THREE (Jupiter primary, Birdeye fallback). Pass usd to also get how much $THREE that amount buys (token amount + atomic units). Read-only — no signer or payment required. It is categorised as a Read tool in the $THREE Token MCP Server, which means it retrieves data without modifying state.
three_price accepts 1 parameter: usd. The full parameter table on this page comes from the server's own tool schema.
Register the $THREE Token MCP server in PolicyLayer and add a rule for three_price: 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 $THREE Token. Nothing to install.
three_price 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 three_price 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 three_price. 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.
three_price is provided by the $THREE Token MCP server (@three-ws/three-token-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on $THREE Token, and thousands of servers like it.
This server
Across the catalogue