get_kaspa_block_prop
Kaspa network health analytics from our own Rusty-Kaspa full node: block-rate progression (blocks/sec, % of 10 bps target), DAA score advancement, tip-parallelism (concurrent chain. $0.08
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-kaspa-block-prop.md
What get_kaspa_block_prop does on Crypto Intelligence
AI agents call get_kaspa_block_prop 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_kaspa_block_prop is rated Low
This is a data retrieval tool that queries blockchain network metrics. It has no side effects, does not modify state, and poses minimal risk even if invoked with arbitrary arguments. The $0.08 cost is incidental infrastructure expense, not a financial transaction by the tool itself.
From the tool's definition Tool retrieves 'Kaspa network health analytics' including 'block-rate progression', 'DAA score advancement', and 'tip-parallelism'—all passive queries of blockchain state data from the server's full node.
Attacks that exploit this kind of access
The rule that runs get_kaspa_block_prop 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_kaspa_block_prop, this is the rule to start with:
get_kaspa_block_prop 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_kaspa_block_prop call is checked against it from then on.
Questions about get_kaspa_block_prop
Kaspa network health analytics from our own Rusty-Kaspa full node: block-rate progression (blocks/sec, % of 10 bps target), DAA score advancement, tip-parallelism (concurrent chain. $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_kaspa_block_prop: 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_kaspa_block_prop 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_kaspa_block_prop 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_kaspa_block_prop. 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_kaspa_block_prop 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