place_flip_order
Place an auto-reversing flip order that provides perpetual liquidity.
This record as markdown: /tools/arome3-tempo-mcp/place-flip-order.md
What place_flip_order does on Tempo
AI agents use place_flip_order to commit financial operations through Tempo, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why place_flip_order is rated Critical
This tool places financial orders on a blockchain stablecoin payment system. 'Flip orders' are trading/liquidity operations that commit financial resources. Given the server is explicitly for 'real-world payments' and 'stablecoin payments', this directly involves financial transactions. The 'perpetual liquidity' aspect means it continuously commits funds, amplifying the blast radius if misused.
From the tool's definition Place an auto-reversing flip order that provides perpetual liquidity
Attacks that exploit this kind of access
The rule that runs place_flip_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For place_flip_order, this is the rule to start with:
Any call to place_flip_order is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every place_flip_order call is checked against it from then on.
Questions about place_flip_order
Place an auto-reversing flip order that provides perpetual liquidity. It is categorised as a Financial tool in the Tempo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tempo MCP server in PolicyLayer and add a rule for place_flip_order: 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 Tempo. Nothing to install.
place_flip_order 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 place_flip_order 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 place_flip_order. 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.
place_flip_order is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tempo, and thousands of servers like it.
Across the catalogue