Pay a Bitcoin Lightning Network invoice through Fiber �?Lightning cross-chain hub.
Part of the Agentpay Dev server.
Free to start. No card required.
AI agents use pay_btc_lightning to initiate financial transactions through Agentpay Dev. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.
pay_btc_lightning moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.
Financial tools involve real money. Block by default and require explicit human approval before enabling.
{
"version": "1",
"default": "deny",
"tools": {
"pay_btc_lightning": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}See the full Agentpay Dev policy for all 8 tools.
These attack patterns abuse exactly the kind of access pay_btc_lightning gives an agent. Each links to the full case and the policy that stops it:
Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Pay a Bitcoin Lightning Network invoice through Fiber �?Lightning cross-chain hub.. It is categorised as a Financial tool in the Agentpay Dev MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agentpay Dev MCP server in PolicyLayer and add a rule for pay_btc_lightning: 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 Agentpay Dev. Nothing to install.
pay_btc_lightning is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pay_btc_lightning 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 pay_btc_lightning. 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.
pay_btc_lightning is provided by the Agentpay Dev MCP server (@agentpay-dev/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Agentpay Dev tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.