get_onchain_pulse
Get Bitcoin on-chain health: mempool congestion, fees, miner distribution, network security, mining economics, and activity levels.
This record as markdown: /tools/0xhashy-fathom-fyi/get-onchain-pulse.md
What get_onchain_pulse does on Fathom Fyi
AI agents call get_onchain_pulse 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_onchain_pulse is rated Low
This tool queries and retrieves blockchain monitoring data without modifying state, executing code, or moving funds. It is purely informational for financial decision-support. While the server context (financial intelligence) is sensitive, this specific tool poses minimal risk—misuse would inform poor trading decisions rather than execute harmful actions directly. Classified as Read with low severity.
From the tool's definition Tool name 'get_onchain_pulse' and description stating it retrieves Bitcoin on-chain metrics: 'mempool congestion, fees, miner distribution, network security, mining economics, and activity levels.' All are read-only data queries with no state changes.
Attacks that exploit this kind of access
The rule that runs get_onchain_pulse 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_onchain_pulse, this is the rule to start with:
get_onchain_pulse 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_onchain_pulse call is checked against it from then on.
Questions about get_onchain_pulse
Get Bitcoin on-chain health: mempool congestion, fees, miner distribution, network security, mining economics, and activity levels. 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_onchain_pulse: 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_onchain_pulse 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_onchain_pulse 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_onchain_pulse. 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_onchain_pulse 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