New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_events_feed

Polling-based event feed — x402-native alternative to push webhooks. $0.10

SERVERCrypto Intelligence SOURCEhttps://api.carbon-cashmere.de/mcp/sse
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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.

Questions about get_events_feed

What does the get_events_feed tool do? +

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.

How do I enforce a policy on get_events_feed? +

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.

What risk level is get_events_feed? +

get_events_feed is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_events_feed? +

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.

How do I block get_events_feed completely? +

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.

What MCP server provides get_events_feed? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crypto Intelligence's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.