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
This record as markdown: /tools/b-open-io-bsv-mcp/bap-getid.md
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. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bap_getId is rated Low
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.
Attacks that exploit this kind of access
The rule that runs bap_getId safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin SV MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bap_getId, this is the rule to start with:
bap_getId 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 Bitcoin SV MCP Server, apply this rule, and every bap_getId call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Bitcoin SV MCP Server MCP Server, which means it retrieves data without modifying state.
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.
bap_getId 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 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.
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.
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.
More on Bitcoin SV MCP Server, and thousands of servers like it.
This server
Across the catalogue