Return historical price snapshots for a symbol (V1.8).
AI agents call get_price_history to retrieve information from OracleForge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches historical price data without side effects. It is a read-only query operation that retrieves data from crypto price feeds. The only potential risk is information disclosure (e.g., if historical prices could leak sensitive trading patterns), but this is low-severity for a public price feed. No write, destructive, execute, or financial action is performed by this tool itself.
From the tool's definition Tool name and description indicate a retrieval operation: 'Return historical price snapshots for a symbol'. No mutation, deletion, or execution of code is indicated.
Attacks that exploit this kind of access
Return historical price snapshots for a symbol (V1.8). It is categorised as a Read tool in the OracleForge MCP MCP Server, which means it retrieves data without modifying state.
Register the OracleForge MCP server in PolicyLayer and add a rule for get_price_history: 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 OracleForge MCP. Nothing to install.
get_price_history 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_price_history 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_price_history. 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_price_history is provided by the OracleForge MCP server (maxiaworld/oracleforge). 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 →