Where are we in the Bitcoin cycle? Get the current bear/bull signal, cycle phase, estimated years to peak, and macro crypto risk level with analyst commentary. Use this when someone asks 'is it time to buy Bitcoin' or 'where are we in the cycle'. Human-curated. Price: $0.10 USDC via x402.
Part of the Crypto Analysis Human MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_narrative_lifecycle to retrieve information from Crypto Analysis Human without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_narrative_lifecycle only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_narrative_lifecycle:
rules:
- action: allowSee the full Crypto Analysis Human policy for all 7 tools.
Where are we in the Bitcoin cycle? Get the current bear/bull signal, cycle phase, estimated years to peak, and macro crypto risk level with analyst commentary. Use this when someone asks 'is it time to buy Bitcoin' or 'where are we in the cycle'. Human-curated. Price: $0.10 USDC via x402.. It is categorised as a Read tool in the Crypto Analysis Human MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_narrative_lifecycle. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Crypto Analysis Human MCP server.
get_narrative_lifecycle 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_narrative_lifecycle rule in your Intercept 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 Intercept policy for get_narrative_lifecycle. 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_narrative_lifecycle is provided by the Crypto Analysis Human MCP server (crypto-analysis-human-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept