# get_latest_block

Get the latest block

Agent View of the PolicyLayer registry record for `get_latest_block`. HTML page: https://policylayer.com/tools/abdelstark-bitcoin-mcp/get-latest-block

## Facts

- Tool: `get_latest_block`
- Server: Bitcoin MCP Server (`abdelstark/bitcoin-mcp`) — https://policylayer.com/tools/abdelstark-bitcoin-mcp.md
- Homepage: https://github.com/AbdelStark/bitcoin-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_latest_block",
    "arguments": {}
  }
}
```

## Why get_latest_block is rated Low

The tool retrieves public blockchain information (the latest block) without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk even if called repeatedly or with unexpected arguments, as it only returns existing immutable data from the Bitcoin network.

From the tool's own definition: "Tool name 'get_latest_block' and description 'Get the latest block' indicate retrieval of blockchain data with no modification or execution of transactions. This is a read-only query operation."

## Use case

AI agents call get_latest_block to retrieve information from Bitcoin MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Bitcoin MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_latest_block": {}
  }
}
```

## Other tools on Bitcoin MCP Server (6)

- `pay_invoice` — Financial — https://policylayer.com/tools/abdelstark-bitcoin-mcp/pay-invoice.md
- `decode_invoice` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/decode-invoice.md
- `decode_tx` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/decode-tx.md
- `get_transaction` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/get-transaction.md
- `validate_address` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/validate-address.md
- `generate_key` — Write — https://policylayer.com/tools/abdelstark-bitcoin-mcp/generate-key.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=abdelstark-bitcoin-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/abdelstark-bitcoin-mcp