get_mempool
Get BTC mempool status from own node — TX count, size, fee estimates, pressure level. $0.03
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-mempool.md
What get_mempool does on Crypto Intelligence
AI agents call get_mempool 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 fee rate histogram |
Parameters from the server's own tool schema.
Why get_mempool is rated Low
This tool only queries and returns information about Bitcoin mempool state. It performs no mutations, executions, deletions, or financial transactions. The $0.03 cost is a micropayment for the query service, not a financial operation by the tool itself. Confidence is high because the description clearly indicates a passive read operation.
From the tool's definition Tool retrieves mempool status (TX count, size, fee estimates, pressure level) from a node. The verb 'Get' and read-only nature of querying mempool data indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_mempool 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_mempool, this is the rule to start with:
get_mempool 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_mempool call is checked against it from then on.
Questions about get_mempool
Get BTC mempool status from own node — TX count, size, fee estimates, pressure level. $0.03. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_mempool 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_mempool: 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_mempool 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_mempool 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_mempool. 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_mempool 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