Returns the raw block representation in binary.
AI agents call esplora_block_raw to retrieve information from Maestro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns existing block data from the Bitcoin blockchain without any side effects. It performs a data retrieval operation analogous to a fetch or get operation. There is no code execution, data modification, financial transaction, or destructive action. The binary format does not change the fundamental read-only nature of the operation.
From the tool's definition Tool name 'esplora_block_raw' and description 'Returns the raw block representation in binary' indicate retrieval of blockchain data with no modification, creation, or deletion of data. This is a read-only query operation.
Documented attack patterns abuse exactly the kind of access esplora_block_raw gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Maestro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for esplora_block_raw:
{
"version": "1",
"default": "deny",
"tools": {
"esplora_block_raw": {}
}
} esplora_block_raw is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the raw block representation in binary. It is categorised as a Read tool in the Maestro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Maestro MCP Server MCP server in PolicyLayer and add a rule for esplora_block_raw: 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 Maestro MCP Server. Nothing to install.
esplora_block_raw 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 esplora_block_raw 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 esplora_block_raw. 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.
esplora_block_raw is provided by the Maestro MCP Server MCP server (maestro-org/maestro-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Maestro MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
117 Maestro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.