get_anomalies
Get ML-detected market anomalies — volume spikes, correlation breaks, structural changes. $0.005
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-anomalies.md
What get_anomalies does on Crypto Intelligence
AI agents call get_anomalies 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 |
|---|---|---|---|
hours | integer | — | Lookback hours (1-24) |
Parameters from the server's own tool schema.
Why get_anomalies is rated Low
This tool queries and returns ML-detected anomalies from market data. It is purely analytical and retrieves information without side effects. The $0.005 micropayment is a usage fee, not indicative of financial transactions or commitments. The tool does not create, modify, delete, or execute any external operations.
From the tool's definition Tool name 'get_anomalies' and description 'Get ML-detected market anomalies' indicate data retrieval only. The description lists outputs: volume spikes, correlation breaks, structural changes — all observational, read-only intelligence.
Attacks that exploit this kind of access
The rule that runs get_anomalies 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_anomalies, this is the rule to start with:
get_anomalies 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_anomalies call is checked against it from then on.
Questions about get_anomalies
Get ML-detected market anomalies — volume spikes, correlation breaks, structural changes. $0.005. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_anomalies accepts 1 parameter: hours. 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_anomalies: 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_anomalies 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_anomalies 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_anomalies. 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_anomalies 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