ios_biometric_auth · LDK MCP Server MCP: Risk & Policy

WHAT IT DOES

What ios_biometric_auth does on LDK MCP Server

AI agents invoke ios_biometric_auth to trigger actions in LDK MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why ios_biometric_auth needs a policy

This tool executes biometric authentication (Touch/Face ID) and wires it into Lightning operations. It's not a pure read (it triggers OS-level auth prompts and integration logic), not destructive or financial on its own, but it executes authentication flows that gate access to sensitive wallet operations. Misuse could bypass or misconfigure security controls.

From the tool's definition 'Integrate Touch/Face ID with Lightning operations' — triggers biometric authentication flows and integrates them with Lightning wallet operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ios_biometric_auth Rate-limited

ios_biometric_auth stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ios_biometric_auth": {
      "limits": [
        {
          "counter": "ios_biometric_auth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about ios_biometric_auth

What does the ios_biometric_auth tool do? +

Integrate Touch/Face ID with Lightning operations. It is categorised as a Execute tool in the LDK MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ios_biometric_auth? +

Register the LDK MCP Server MCP server in PolicyLayer and add a rule for ios_biometric_auth: 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 LDK MCP Server. Nothing to install.

What risk level is ios_biometric_auth? +

ios_biometric_auth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ios_biometric_auth? +

Yes. Add a rate_limit block to the ios_biometric_auth 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 ios_biometric_auth completely? +

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

ios_biometric_auth is provided by the LDK MCP Server MCP server (stevengeller/ldk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.