Register a new AI agent account with LQWD. Returns an API key and, when you supply a Lightning node's pubkey + node_uri, a one-time inbound channel on mainnet as part of the tier-1 faucet grant. Always free; no authentication required — this tool is how you GET your API key. To receive an inbound...
Part of the LQWD Gateway server.
Free to start. No card required.
AI agents use lqwd_register to create or modify resources in LQWD Gateway. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call lqwd_register repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach LQWD Gateway.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"lqwd_register": {
"limits": [
{
"counter": "lqwd_register_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full LQWD Gateway policy for all 3 tools.
These attack patterns abuse exactly the kind of access lqwd_register gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Register a new AI agent account with LQWD. Returns an API key and, when you supply a Lightning node's pubkey + node_uri, a one-time inbound channel on mainnet as part of the tier-1 faucet grant. Always free; no authentication required — this tool is how you GET your API key. To receive an inbound channel from LQWD, pass pubkey AND node_uri together.. It is categorised as a Write tool in the LQWD Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LQWD Gateway MCP server in PolicyLayer and add a rule for lqwd_register: 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 LQWD Gateway. Nothing to install.
lqwd_register 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 lqwd_register 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 lqwd_register. 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.
lqwd_register is provided by the LQWD Gateway MCP server (https://api.lqwdclaw.bot/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 LQWD Gateway 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.