AI agents invoke lithtrix_passport_rotate 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.
This tool rotates a cryptographic identity key (Ed25519 passport), which is an irreversible credential operation — the old key is invalidated and the new private key is returned only once. Misuse by an AI agent could permanently compromise the agent's identity/authentication, lock out legitimate owners, or expose the private key.
From the tool's definition rotate Ed25519 passport (requires **root** LITHTRIX_API_KEY). Returns private_key once.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
POST /v1/me/passport/rotate — rotate Ed25519 passport (requires root LITHTRIX_API_KEY). Returns private_key once. 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.
Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_passport_rotate: 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.
lithtrix_passport_rotate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lithtrix_passport_rotate 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 lithtrix_passport_rotate. 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.
lithtrix_passport_rotate 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →