Place a resting limit order on the stablecoin DEX orderbook.
AI agents use place_limit_order to commit financial operations through Tempo — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool places a financial order on a decentralized exchange orderbook, committing to a trade of stablecoin assets. It directly involves financial obligations and asset movements, making it Financial category. The blast radius is critical as an AI agent could place large or unintended orders on a DEX, resulting in significant financial loss or unwanted asset swaps.
From the tool's definition Place a resting limit order on the stablecoin DEX orderbook
Documented attack patterns abuse exactly the kind of access place_limit_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tempo, and nothing reaches the server without passing your rules. This is the rule we recommend for place_limit_order:
{
"version": "1",
"default": "deny",
"tools": {
"place_limit_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to place_limit_order is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Place a resting limit order on the stablecoin DEX orderbook. 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_limit_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_limit_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_limit_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_limit_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_limit_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.
Start from Tempo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
61 Tempo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.