danke_register · Danke MCP: Risk & Policy

WHAT IT DOES

What danke_register does on Danke

AI agents use danke_register to commit financial operations through Danke — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why danke_register needs a policy

Registration on a financial network (Bitcoin Lightning) creates an account/identity that enables financial transactions (earning and sending sats). While registration itself doesn't move money, it initiates a financial relationship and is a prerequisite for financial operations on the Danke network.

From the tool's definition Register this agent on the Danke network to start earning sats

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

danke_register Approval-gated

Any call to danke_register is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "danke_register": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Danke, so you can run agents against it safely.

FAQ

Questions about danke_register

What does the danke_register tool do? +

Register this agent on the Danke network to start earning sats. Idempotent — safe to call multiple times. It is categorised as a Financial tool in the Danke MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on danke_register? +

Register the Danke MCP server in PolicyLayer and add a rule for danke_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 Danke. Nothing to install.

What risk level is danke_register? +

danke_register is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit danke_register? +

Yes. Add a rate_limit block to the danke_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.

How do I block danke_register completely? +

Set action: deny in the PolicyLayer policy for danke_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.

What MCP server provides danke_register? +

danke_register is provided by the Danke MCP server (jordiagi/danke-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.