Publish an MCP tool configuration record on-chain via Ordinal inscription. This creates a permanent, immutable, and discoverable tool definition that can be accessed by other MCP servers. The tool is published as a JSON inscription with metadata and optional digital signatures for authenticity ve...
AI agents use wallet_a2bPublishMcp 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.
While publishing is technically a write operation (creates/modifies data reversibly in the sense that new records are added), the immutable nature of blockchain inscriptions and the permanent financial commitment required to write to the BSV blockchain elevate this beyond a simple write.
From the tool's definition Publishes data on-chain via Ordinal inscription creating a permanent record. Description explicitly states 'Publish an MCP tool configuration record on-chain' and 'creates a permanent, immutable' inscription.
Documented attack patterns abuse exactly the kind of access wallet_a2bPublishMcp 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 wallet_a2bPublishMcp:
{
"version": "1",
"default": "deny",
"tools": {
"wallet_a2bPublishMcp": {
"limits": [
{
"counter": "wallet_a2bpublishmcp_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wallet_a2bPublishMcp 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.
Publish an MCP tool configuration record on-chain via Ordinal inscription. This creates a permanent, immutable, and discoverable tool definition that can be accessed by other MCP servers. The tool is published as a JSON inscription with metadata and optional digital signatures for authenticity verification. 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 wallet_a2bPublishMcp: 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.
wallet_a2bPublishMcp 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 wallet_a2bPublishMcp 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 wallet_a2bPublishMcp. 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.
wallet_a2bPublishMcp 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.