get_signals
Get real-time trading signals — funding extreme, liquidation cascade, confluence. $0.005
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-signals.md
What get_signals does on Crypto Intelligence
AI agents call get_signals 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 |
|---|---|---|---|
symbol | string | — | Filter by coin symbol (BTC, ETH, SOL) |
severity | string | — | Minimum severity: low, medium, high, critical |
signal_type | string | — | Filter by type: confluence, funding_extreme, liquidation_cascade, volume_anomaly |
Parameters from the server's own tool schema.
Why get_signals is rated Low
This tool retrieves and queries trading intelligence signals in real-time. It has no side effects: it does not execute trades, modify market state, move funds, or trigger external operations. The signals are informational outputs to support decision-making. While the server context involves financial assets (crypto trading), this specific tool is read-only data retrieval.
From the tool's definition Tool name 'get_signals' and description 'Get real-time trading signals — funding extreme, liquidation cascade, confluence' describe retrieval of analytical data.
Attacks that exploit this kind of access
The rule that runs get_signals 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_signals, this is the rule to start with:
get_signals 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_signals call is checked against it from then on.
Questions about get_signals
Get real-time trading signals — funding extreme, liquidation cascade, confluence. $0.005. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_signals accepts 3 parameters: symbol, severity, signal_type. 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_signals: 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_signals 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_signals 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_signals. 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_signals 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