get_historical_context
Look up what market conditions were on a specific date. Returns regime, fear/greed, risk score, BTC price, and TVL from that date. Useful for comparing past conditions to current ones.
This record as markdown: /tools/0xhashy-fathom-fyi/get-historical-context.md
What get_historical_context does on Fathom Fyi
AI agents call get_historical_context to retrieve information from Fathom Fyi without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_historical_context is rated Low
This tool retrieves historical market data for comparison and analysis purposes. It performs no mutations, deletions, executions, or financial transactions. Even in a financial intelligence context, querying historical context is fundamentally a read operation with minimal risk—the worst outcome of misuse would be incorrect analysis based on valid but misinterpreted historical data, not damage to systems or accounts.
From the tool's definition Tool name 'get_historical_context' and description 'Look up what market conditions were on a specific date. Returns regime, fear/greed, risk score, BTC price, and TVL from that date.' indicate pure data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_historical_context safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fathom Fyi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_historical_context, this is the rule to start with:
get_historical_context 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 Fathom Fyi, apply this rule, and every get_historical_context call is checked against it from then on.
Questions about get_historical_context
Look up what market conditions were on a specific date. Returns regime, fear/greed, risk score, BTC price, and TVL from that date. Useful for comparing past conditions to current ones. It is categorised as a Read tool in the Fathom Fyi MCP Server, which means it retrieves data without modifying state.
Register the Fathom Fyi MCP server in PolicyLayer and add a rule for get_historical_context: 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 Fathom Fyi. Nothing to install.
get_historical_context 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_historical_context 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_historical_context. 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_historical_context is provided by the Fathom Fyi MCP server (0xhashy/fathom-fyi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fathom Fyi, and thousands of servers like it.
This server
Across the catalogue