lithtrix_passport_auth_verify · Lithtrix MCP: Risk & Policy

WHAT IT DOES

What lithtrix_passport_auth_verify does on Lithtrix

AI agents invoke lithtrix_passport_auth_verify to trigger actions in Lithtrix. 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 lithtrix_passport_auth_verify needs a policy

This tool performs an authentication operation that exchanges a cryptographic signature for a session token. It triggers an external operation (POST to an auth endpoint) whose effect is issuing a persistent session credential (ltx_session_*). This is not a simple read — it creates a session token and has side effects.

From the tool's definition POST /v1/auth/passport/verify — exchange Ed25519 signature for ltx_session_* token

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lithtrix_passport_auth_verify Rate-limited

lithtrix_passport_auth_verify 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": {
    "lithtrix_passport_auth_verify": {
      "limits": [
        {
          "counter": "lithtrix_passport_auth_verify_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 Lithtrix, so you can run agents against it safely.

FAQ

Questions about lithtrix_passport_auth_verify

What does the lithtrix_passport_auth_verify tool do? +

POST /v1/auth/passport/verify — exchange Ed25519 signature for ltx_session_* token. It is categorised as a Execute tool in the Lithtrix MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lithtrix_passport_auth_verify? +

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

What risk level is lithtrix_passport_auth_verify? +

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

Can I rate-limit lithtrix_passport_auth_verify? +

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

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

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