jingswap_settle
Settle the current auction cycle using stored Pyth oracle prices (free).
This record as markdown: /tools/io-github-aibtcdev-mcp-server/jingswap-settle.md
What jingswap_settle does on Aibtc
AI agents use jingswap_settle to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why jingswap_settle is rated Critical
Settling an auction cycle is a financial operation that irreversibly finalizes the outcome of an auction, committing funds based on Pyth oracle prices. This is a financial action that cannot be undone and affects user balances or positions.
From the tool's definition 'Settle the current auction cycle' — settling an auction cycle is a financial commitment that finalizes trades/orders and moves funds based on oracle prices
Attacks that exploit this kind of access
The rule that runs jingswap_settle safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jingswap_settle, this is the rule to start with:
Any call to jingswap_settle is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every jingswap_settle call is checked against it from then on.
Questions about jingswap_settle
Settle the current auction cycle using stored Pyth oracle prices (free). It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for jingswap_settle: 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 Aibtc. Nothing to install.
jingswap_settle 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 jingswap_settle 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 jingswap_settle. 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.
jingswap_settle is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue