get_onchain_pulse
BTC on-chain pulse analytics from our own Bitcoin Core full node — mempool pressure z-score over 30d, hashrate 7d/30d momentum with trend classification (expanding/stable/contracti. $0.15
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-onchain-pulse.md
What get_onchain_pulse does on Crypto Intelligence
AI agents call get_onchain_pulse to retrieve information from Crypto Intelligence 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 retrieves and calculates blockchain analytics metrics (mempool pressure z-scores, hashrate momentum, trend classification) from the operator's own Bitcoin node. It performs no modifications to data, executes no external code or operations, deletes nothing, and incurs no financial obligation—it is purely an informational read operation with a nominal data access fee.
From the tool's definition Tool name 'get_onchain_pulse' and description 'BTC on-chain pulse analytics from our own Bitcoin Core full node — mempool pressure z-score over 30d, hashrate 7d/30d momentum with trend classification'. Returns calculated metrics and analytics only. Cost is $0.
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 Crypto Intelligence, 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 Crypto Intelligence, apply this rule, and every get_onchain_pulse call is checked against it from then on.
Questions about get_onchain_pulse
BTC on-chain pulse analytics from our own Bitcoin Core full node — mempool pressure z-score over 30d, hashrate 7d/30d momentum with trend classification (expanding/stable/contracti. $0.15. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Crypto Intelligence 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 Crypto Intelligence. 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 Crypto Intelligence MCP server (https://api.carbon-cashmere.de/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crypto Intelligence, and thousands of servers like it.
This server
Across the catalogue