get_eco_watch
Ecosystem Watch — budget market pulse: current regime + fear/greed index + 30d rotation (34-coin cross-sectional) + signal activity 24h. $0.08
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-eco-watch.md
What get_eco_watch does on Crypto Intelligence
AI agents call get_eco_watch 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_eco_watch is rated Low
This tool retrieves and aggregates cryptocurrency market intelligence (fear/greed metrics, asset rotation patterns, signal data) without side effects. It is a pure read operation that queries market analytics. While the server context mentions 'trading intelligence' and micropayments, this specific tool does not execute trades, move funds, or modify any state—it only surfaces market data for analysis.
From the tool's definition Tool name 'get_eco_watch' and description 'current regime + fear/greed index + 30d rotation + signal activity 24h' indicate retrieval of market analytics and sentiment data. The '$0.08' cost confirms it is a query operation.
Attacks that exploit this kind of access
The rule that runs get_eco_watch 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_eco_watch, this is the rule to start with:
get_eco_watch 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_eco_watch call is checked against it from then on.
Questions about get_eco_watch
Ecosystem Watch — budget market pulse: current regime + fear/greed index + 30d rotation (34-coin cross-sectional) + signal activity 24h. $0.08. 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_eco_watch: 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_eco_watch 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_eco_watch 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_eco_watch. 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_eco_watch 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