AI agents use lithtrix_passport_stake to commit financial operations through Lithtrix — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool locks/commits platform credits (a financial resource) to stake a tier. Staking involves locking funds or credits that create financial obligations and cannot be trivially reversed. This falls squarely in the Financial category as it moves or commits financial value. Misuse by an AI agent could result in irreversible financial commitments of platform credits.
From the tool's definition lock platform credits for passport stake tier
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
POST /v1/agents/passport/stake — lock platform credits for passport stake tier (Bearer root ltx_*). It is categorised as a Financial tool in the Lithtrix MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_passport_stake: 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_stake is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the lithtrix_passport_stake 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_stake. 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_stake 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 →