Configure LNbits connection parameters at runtime.
AI agents use configure_lnbits to create or update resources in LNbits MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LNbits MCP Server environment.
This tool creates or modifies configuration data at runtime. It does not delete or purge data (not Destructive), does not move money (not Financial), and does not execute arbitrary code (not Execute). However, the severity is high because misconfigured connection parameters could compromise wallet security, expose credentials, or redirect payments to attacker-controlled endpoints.
From the tool's definition Tool description states 'Configure LNbits connection parameters at runtime' — this modifies configuration settings that govern how the LNbits wallet system operates.
Documented attack patterns abuse exactly the kind of access configure_lnbits gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LNbits MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for configure_lnbits:
{
"version": "1",
"default": "deny",
"tools": {
"configure_lnbits": {
"limits": [
{
"counter": "configure_lnbits_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}configure_lnbits 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.
Configure LNbits connection parameters at runtime. It is categorised as a Write tool in the LNbits MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LNbits MCP Server MCP server in PolicyLayer and add a rule for configure_lnbits: 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 LNbits MCP Server. Nothing to install.
configure_lnbits 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 configure_lnbits 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 configure_lnbits. 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.
configure_lnbits is provided by the LNbits MCP Server MCP server (lnbits/lnbits-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LNbits 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.
6 LNbits MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.