Get historical spot price feed data (index prices) with timestamps.
AI agents call get_spot_feed_history to retrieve information from Derive MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical spot price data without side effects. It performs a read-only query operation that simply fetches existing price information. There is no capacity to modify data, execute trades, delete records, or commit financial transactions. The low severity reflects minimal risk even in misuse scenarios, as historical data retrieval cannot directly harm trading positions or accounts.
From the tool's definition Tool name 'get_spot_feed_history' and description 'Get historical spot price feed data (index prices) with timestamps' indicate retrieval of historical market data with no modification or execution capability.
Attacks that exploit this kind of access
Get historical spot price feed data (index prices) with timestamps. It is categorised as a Read tool in the Derive MCP MCP Server, which means it retrieves data without modifying state.
Register the Derive MCP server in PolicyLayer and add a rule for get_spot_feed_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 Derive MCP. Nothing to install.
get_spot_feed_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_spot_feed_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_spot_feed_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_spot_feed_history is provided by the Derive MCP server (solenyaresearch0000/derive-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 →