set_budget
Set or update budget limit for an agent. REQUIRES OPERATOR KEY.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/set-budget.md
What set_budget does on Lightning Wallet
AI agents use set_budget to commit financial operations through Lightning Wallet, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why set_budget is rated Critical
This tool governs financial spending limits for agents on a Bitcoin/Lightning wallet platform. Setting or updating a budget directly affects financial obligations and spending authority. Misuse could allow an agent to spend far more (or less) than intended, making this a Financial category tool with high severity.
From the tool's definition 'Set or update budget limit for an agent' on a Bitcoin Lightning Wallet server — controls how much an agent can spend financially
Attacks that exploit this kind of access
The rule that runs set_budget safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lightning Wallet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_budget, this is the rule to start with:
Any call to set_budget is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Lightning Wallet, apply this rule, and every set_budget call is checked against it from then on.
Questions about set_budget
Set or update budget limit for an agent. REQUIRES OPERATOR KEY. It is categorised as a Financial tool in the Lightning Wallet MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Lightning Wallet MCP server in PolicyLayer and add a rule for set_budget: 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 Lightning Wallet. Nothing to install.
set_budget 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 set_budget 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 set_budget. 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.
set_budget is provided by the Lightning Wallet MCP server (lightning-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lightning Wallet, and thousands of servers like it.
Across the catalogue