get_consensus
Get accuracy-weighted consensus from 4 AI prediction agents for 34 coins. $0.08
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-consensus.md
What get_consensus does on Crypto Intelligence
AI agents call get_consensus 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
coin | string | — | Filter by coin (BTC, ETH, SOL) |
Parameters from the server's own tool schema.
Why get_consensus is rated Low
This tool retrieves consensus predictions from AI agents—a read operation. Although the server context mentions financial operations (micropayments, trading), this specific tool does not execute trades, move funds, or create financial commitments. The small charge is a usage fee, not a financial trade. Confidence is high because the description clearly indicates a query/retrieval function with no side effects.
From the tool's definition Tool name 'get_consensus' and description 'Get accuracy-weighted consensus from 4 AI prediction agents for 34 coins' indicate data retrieval with no modifications.
Attacks that exploit this kind of access
The rule that runs get_consensus 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_consensus, this is the rule to start with:
get_consensus 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_consensus call is checked against it from then on.
Questions about get_consensus
Get accuracy-weighted consensus from 4 AI prediction agents for 34 coins. $0.08. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_consensus accepts 1 parameter: coin. The full parameter table on this page comes from the server's own tool schema.
Register the Crypto Intelligence MCP server in PolicyLayer and add a rule for get_consensus: 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_consensus 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_consensus 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_consensus. 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_consensus 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