Initiates a friend request to another BAP ID by broadcasting an on-chain MAP transaction.
AI agents invoke bap_friend to trigger actions in Bitcoin SV MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool broadcasts a transaction to the BSV blockchain, which is an irreversible on-chain action. While not financial or destructive in the traditional sense, it executes an external blockchain operation with permanent effects. Broadcasting transactions cannot be undone once confirmed on-chain, making this an Execute-category action with high severity due to the permanent, public nature of blockchain writes.
From the tool's definition Initiates a friend request to another BAP ID by broadcasting an on-chain MAP transaction
Documented attack patterns abuse exactly the kind of access bap_friend 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_friend:
{
"version": "1",
"default": "deny",
"tools": {
"bap_friend": {
"limits": [
{
"counter": "bap_friend_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} bap_friend stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Initiates a friend request to another BAP ID by broadcasting an on-chain MAP transaction. It is categorised as a Execute tool in the Bitcoin SV MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for bap_friend: 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_friend is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bap_friend 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_friend. 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_friend 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.