get_eth_beacon
Get Ethereum beacon chain status from own Nimbus full node — slot, epoch, finality gap, peers. $0.002
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-eth-beacon.md
What get_eth_beacon does on Crypto Intelligence
AI agents call get_eth_beacon 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 |
|---|---|---|---|
detail | boolean | — | Include validator stats |
Parameters from the server's own tool schema.
Why get_eth_beacon is rated Low
This tool performs a straightforward read operation querying the status of an Ethereum beacon chain node. It retrieves immutable state information without side effects, modifications, execution of arbitrary code, deletion, or financial transactions. The tool is purely informational.
From the tool's definition Tool description states 'Get Ethereum beacon chain status' which retrieves data (slot, epoch, finality gap, peers) from the node with no modification or execution capability mentioned. The cost of $0.002 indicates a query operation.
Attacks that exploit this kind of access
The rule that runs get_eth_beacon 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_eth_beacon, this is the rule to start with:
get_eth_beacon 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_eth_beacon call is checked against it from then on.
Questions about get_eth_beacon
Get Ethereum beacon chain status from own Nimbus full node — slot, epoch, finality gap, peers. $0.002. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_eth_beacon accepts 1 parameter: detail. 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_eth_beacon: 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_eth_beacon 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_eth_beacon 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_eth_beacon. 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_eth_beacon 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