get_dispersion
Cross-sectional dispersion metrics: cross-sectional volatility (std across coins per timestamp, averaged over period), hierarchical correlation clusters (2-5 groups, avg intra-clus. $0.10
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-dispersion.md
What get_dispersion does on Crypto Intelligence
AI agents call get_dispersion 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_dispersion is rated Low
get_dispersion is a pure query/analytics tool that computes statistical measures across cryptocurrency data. It retrieves and processes data without side effects—no reversible writes, no code execution, no destructive operations, and no direct financial transfers initiated by the tool.
From the tool's definition Tool retrieves and calculates analytical metrics (cross-sectional volatility, correlation clusters) from existing data. Verbs are computational/analytical: 'metrics', 'std', 'averaged', 'clusters'.
Attacks that exploit this kind of access
The rule that runs get_dispersion 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_dispersion, this is the rule to start with:
get_dispersion 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_dispersion call is checked against it from then on.
Questions about get_dispersion
Cross-sectional dispersion metrics: cross-sectional volatility (std across coins per timestamp, averaged over period), hierarchical correlation clusters (2-5 groups, avg intra-clus. $0.10. 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_dispersion: 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_dispersion 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_dispersion 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_dispersion. 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_dispersion 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