Generates a BAP HD master key AND derives the first identity key if no BAP keys (xprv or identityPk) exist. Saves keys to secure storage. Attempts on-chain registration using payPk (honors DISABLE_BROADCASTING). Optionally takes alternateName and description for the profile.
AI agents use bap_generate to create or update resources in Bitcoin SV MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitcoin SV MCP Server environment.
The tool creates new cryptographic material (HD master keys, identity keys) and persists them to secure storage, which are irreversible write operations. It also initiates on-chain registration, a blockchain write operation. While it involves blockchain interaction and key generation, it does not transfer funds (Financial) or delete data (Destructive).
From the tool's definition Tool generates and saves cryptographic keys to storage ('Generates a BAP HD master key AND derives the first identity key', 'Saves keys to secure storage'), and performs on-chain registration operations ('Attempts on-chain registration').
Documented attack patterns abuse exactly the kind of access bap_generate gives an agent:
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_generate:
{
"version": "1",
"default": "deny",
"tools": {
"bap_generate": {
"limits": [
{
"counter": "bap_generate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bap_generate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generates a BAP HD master key AND derives the first identity key if no BAP keys (xprv or identityPk) exist. Saves keys to secure storage. Attempts on-chain registration using payPk (honors DISABLE_BROADCASTING). Optionally takes alternateName and description for the profile. It is categorised as a Write tool in the Bitcoin SV MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for bap_generate: 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_generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bap_generate 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_generate. 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_generate 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.
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.