apro-ticker-currency-support
APRO v2 GET /v2/ticker/currency/support: metadata and supported providers for one currency. Query param restricted must be strict or relaxed. Docs: https://docs.apro.com/ai-oracle/getting-started/quickstart/apro-ai-oracle-api-v2/ticker
This record as markdown: /tools/demomagic-lucy-apro/apro-ticker-currency-support.md
What apro-ticker-currency-support does on Lucy Apro
AI agents call apro-ticker-currency-support to retrieve information from Lucy Apro 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 |
|---|---|---|---|
name | string | — | Single currency to look up: canonical name, symbol, or keyword (e.g. link for Chainlink). One asset only. |
restricted | string | — | strict (default): require at least 3 data sources. relaxed: looser matching. Only these two lowercase strings; no synonyms. |
Parameters from the server's own tool schema.
Why apro-ticker-currency-support is rated Low
This tool is a simple data retrieval endpoint that queries metadata about currency support and available providers. It uses HTTP GET, accepts only filtering query parameters (strict/relaxed restriction mode), and returns informational data with no side effects. It is consistent with sibling tools like apro-ticker-currencies-list and apro-ticker-currency-price which are all read-only ticker data queries.
From the tool's definition GET /v2/ticker/currency/support retrieves metadata and supported providers for one currency; no modification, deletion, or execution of external operations occurs
Attacks that exploit this kind of access
The rule that runs apro-ticker-currency-support safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lucy Apro, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For apro-ticker-currency-support, this is the rule to start with:
apro-ticker-currency-support 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 Lucy Apro, apply this rule, and every apro-ticker-currency-support call is checked against it from then on.
Questions about apro-ticker-currency-support
APRO v2 GET /v2/ticker/currency/support: metadata and supported providers for one currency. Query param restricted must be strict or relaxed. Docs: https://docs.apro.com/ai-oracle/getting-started/quickstart/apro-ai-oracle-api-v2/ticker. It is categorised as a Read tool in the Lucy Apro MCP Server, which means it retrieves data without modifying state.
apro-ticker-currency-support accepts 2 parameters: name, restricted. The full parameter table on this page comes from the server's own tool schema.
Register the Lucy Apro MCP server in PolicyLayer and add a rule for apro-ticker-currency-support: 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 Lucy Apro. Nothing to install.
apro-ticker-currency-support 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 apro-ticker-currency-support 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 apro-ticker-currency-support. 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.
apro-ticker-currency-support is provided by the Lucy Apro MCP server (demomagic/lucy-apro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lucy Apro, and thousands of servers like it.
This server
Across the catalogue