get_spot_feed_history
Get historical spot price data for a currency
This record as markdown: /tools/aadarshvelu-derive-mcp/get-spot-feed-history.md
What get_spot_feed_history does on Derive MCP Server
AI agents call get_spot_feed_history to retrieve information from Derive MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_spot_feed_history is rated Low
This tool queries and retrieves historical spot price data from the Derive.xyz API. It is a read-only operation with no side effects, no code execution, and no financial transactions. The blast radius of misuse is minimal—an agent could only access publicly available market data already exposed by the unauthenticated REST API. It aligns with the 'Read' category: retrieves or queries data with no side effects.
From the tool's definition Tool name 'get_spot_feed_history' and description 'Get historical spot price data for a currency' indicate a data retrieval operation. No modifications, deletions, or external operations are performed.
Attacks that exploit this kind of access
The rule that runs get_spot_feed_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Derive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_spot_feed_history, this is the rule to start with:
get_spot_feed_history 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 Derive MCP Server, apply this rule, and every get_spot_feed_history call is checked against it from then on.
Questions about get_spot_feed_history
Get historical spot price data for a currency. It is categorised as a Read tool in the Derive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Derive MCP Server 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 Server. 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 MCP server (aadarshvelu/derive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Derive MCP Server, and thousands of servers like it.
This server
Across the catalogue