get_signal_history

[BETA] View Fathom\

SERVERFathom Fyi SOURCE0xhashy/fathom-fyi
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/0xhashy-fathom-fyi/get-signal-history.md

What get_signal_history does on Fathom Fyi

AI agents call get_signal_history 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_signal_history is rated Low

This tool retrieves historical signal data with no side effects. Even in a financial context, viewing historical signals is informational (Read category) rather than executing trades (Execute), moving money (Financial), or deleting data (Destructive). The low severity reflects that misuse would only allow an agent to access past data, not commit actual financial transactions or cause irreversible harm.

From the tool's definition Tool name 'get_signal_history' indicates historical data retrieval. Description is truncated ('View Fathom\') but the name and context (financial intelligence data sources for AI agents) suggest querying past signal data rather than executing trades or…

Questions about get_signal_history

What does the get_signal_history tool do? +

[BETA] View Fathom\. It is categorised as a Read tool in the Fathom Fyi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_signal_history? +

Register the Fathom Fyi MCP server in PolicyLayer and add a rule for get_signal_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 Fathom Fyi. Nothing to install.

What risk level is get_signal_history? +

get_signal_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_signal_history? +

Yes. Add a rate_limit block to the get_signal_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.

How do I block get_signal_history completely? +

Set action: deny in the PolicyLayer policy for get_signal_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.

What MCP server provides get_signal_history? +

get_signal_history 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Fathom Fyi's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.