AI agents call get_settlement to retrieve information from Luxxon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_settlement queries and returns data about a completed settlement (state machine status and txHash) without creating, modifying, or executing any operations. It is a passive information retrieval operation. Although this is a financial application (USDC settlement on Base), the tool itself only reads settlement status—it does not move money, approve transactions, or commit financial obligations.
From the tool's definition Tool name and description indicate retrieval of settlement state and transaction hash: 'On-chain settlement state + tx hash for a session after end_session.' No mutations, deletions, financial transactions, or code execution.
Attacks that exploit this kind of access
On-chain settlement state + tx hash for a session after end_session. State machine: NOT_READY → PENDING → SUBMITTED → CONFIRMED. txHash is set once SUBMITTED. It is categorised as a Read tool in the Luxxon MCP Server, which means it retrieves data without modifying state.
Register the Luxxon MCP server in PolicyLayer and add a rule for get_settlement: 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 Luxxon. Nothing to install.
get_settlement is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_settlement 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 get_settlement. 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.
get_settlement is provided by the Luxxon MCP server (luxxon-dev/luxxon-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_settlement is one line of Luxxon's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →