Low Risk

bap_getId

Retrieves a Bitcoin Attestation Protocol (BAP) identity profile using an idKey (Paymail or public key). If no idKey is provided, it attempts to use the server

How to control bap_getId ↓

What bap_getId does on Bitcoin SV MCP Server

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

Low Risk

Why bap_getId needs a policy

The tool retrieves identity profile information from the blockchain using an idKey parameter. This is a query/lookup operation with no ability to modify, delete, execute arbitrary code, or commit financial transactions. The blast radius of misuse is minimal—worst case would be retrieving identity information that is already public on the blockchain.

From the tool's definition Tool name 'bap_getId' and description 'Retrieves a Bitcoin Attestation Protocol (BAP) identity profile' explicitly indicate a read operation that fetches data without modification or side effects.

Documented attack patterns abuse exactly the kind of access bap_getId gives an agent:

How to control bap_getId

PolicyLayer is an MCP gateway — it sits between your AI agents and Bitcoin SV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bap_getId:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "bap_getId": {}
  }
}

bap_getId is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Bitcoin SV MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about bap_getId

What does the bap_getId tool do? +

Retrieves a Bitcoin Attestation Protocol (BAP) identity profile using an idKey (Paymail or public key). If no idKey is provided, it attempts to use the server. It is categorised as a Read tool in the Bitcoin SV MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bap_getId? +

Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for bap_getId: 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 Bitcoin SV MCP Server. Nothing to install.

What risk level is bap_getId? +

bap_getId is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bap_getId? +

Yes. Add a rate_limit block to the bap_getId 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.

How do I block bap_getId completely? +

Set action: deny in the PolicyLayer policy for bap_getId. 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.

What MCP server provides bap_getId? +

bap_getId is provided by the Bitcoin SV MCP Server MCP server (b-open-io/bsv-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bitcoin SV MCP Server tool call.

Start from Bitcoin SV 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.

80 Bitcoin SV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.