get_events_feed
Polling-based event feed — x402-native alternative to push webhooks. $0.10
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-events-feed.md
What get_events_feed does on Crypto Intelligence
AI agents call get_events_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.
Why get_events_feed is rated Low
This tool queries or retrieves event data via polling, which is a read-only operation with no side effects. It has no capability to create, modify, delete, execute code, or move funds. The micropayment is incidental to access, not indicative of financial risk. The low blast radius reflects that misuse would only expose or retrieve existing event data.
From the tool's definition get_events_feed is described as a 'Polling-based event feed' that retrieves data, with no indication of state modification, deletion, or external execution. The $0.10 cost is a micropayment for the read operation.
Attacks that exploit this kind of access
The rule that runs get_events_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_events_feed, this is the rule to start with:
get_events_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_events_feed call is checked against it from then on.
Questions about get_events_feed
Polling-based event feed — x402-native alternative to push webhooks. $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_events_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_events_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_events_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_events_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_events_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