lookup_currency_historical
Get a historical FX rate. Pass base/target/date (YYYY-MM-DD). Use for accounting backfill or historical-analysis agents. Example call: {"base_target_date": "USD/EUR/2024-01-15"} Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/lookup-currency-historical.md
What lookup_currency_historical does on GoCreative Agent API
AI agents call lookup_currency_historical to retrieve information from GoCreative Agent API 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 |
|---|---|---|---|
base_target_date | string | Yes |
Parameters from the server's own tool schema.
Why lookup_currency_historical is rated Low
This tool queries historical foreign exchange data and returns information without modifying, executing code, deleting data, or moving money. It is purely a data lookup operation. While the server context mentions financial aspects (USDC payments, x402), this particular tool only retrieves historical rate information for analysis purposes.
From the tool's definition Tool description states 'Get a historical FX rate' with parameters base/target/date. Example call retrieves USD/EUR/2024-01-15.
Attacks that exploit this kind of access
The rule that runs lookup_currency_historical safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoCreative Agent API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lookup_currency_historical, this is the rule to start with:
lookup_currency_historical 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 GoCreative Agent API, apply this rule, and every lookup_currency_historical call is checked against it from then on.
Questions about lookup_currency_historical
Get a historical FX rate. Pass base/target/date (YYYY-MM-DD). Use for accounting backfill or historical-analysis agents. Example call: {"base_target_date": "USD/EUR/2024-01-15"} Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the GoCreative Agent API MCP Server, which means it retrieves data without modifying state.
lookup_currency_historical accepts 1 parameter: base_target_date. Required: base_target_date. The full parameter table on this page comes from the server's own tool schema.
Register the GoCreative Agent API MCP server in PolicyLayer and add a rule for lookup_currency_historical: 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 GoCreative Agent API. Nothing to install.
lookup_currency_historical 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 lookup_currency_historical 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 lookup_currency_historical. 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.
lookup_currency_historical is provided by the GoCreative Agent API MCP server (https://api.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoCreative Agent API, and thousands of servers like it.
This server
Across the catalogue