get_signal_feed
Multi-coin ML trading signals — direction, probability, confidence, track record. $0.01
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-signal-feed.md
What get_signal_feed does on Crypto Intelligence
AI agents call get_signal_feed 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 |
|---|---|---|---|
coins | string | — | Comma-separated coins. Omit for all |
actionable_only | boolean | — | Only actionable signals |
Parameters from the server's own tool schema.
Why get_signal_feed is rated Low
This tool fetches historical or current trading signal data—analysis outputs that inform trading decisions but do not execute trades, transfer assets, or modify state. It is informational intelligence gathering. The micropayment is the *cost* to access the service, not a financial commitment or transfer initiated by the tool itself.
From the tool's definition Tool name 'get_signal_feed' and description indicate retrieval of pre-computed ML trading signals (direction, probability, confidence, track record). The verb 'get' and the data-retrieval nature ('signals', 'track record') confirm this is a query operation.
Attacks that exploit this kind of access
The rule that runs get_signal_feed 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_signal_feed, this is the rule to start with:
get_signal_feed 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_signal_feed call is checked against it from then on.
Questions about get_signal_feed
Multi-coin ML trading signals — direction, probability, confidence, track record. $0.01. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_signal_feed accepts 2 parameters: coins, actionable_only. 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_signal_feed: 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_signal_feed 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_signal_feed 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_signal_feed. 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_signal_feed 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