get_my_orders
List your open orders on the DEX. Can filter by token and status.
This record as markdown: /tools/arome3-tempo-mcp/get-my-orders.md
What get_my_orders does on Tempo
AI agents call get_my_orders to retrieve information from Tempo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_my_orders is rated Low
This tool retrieves and queries data about the user's open orders with optional filtering. It has no side effects, does not modify or delete data, and does not execute external operations or move funds. It is a straightforward data retrieval function typical of exchange query APIs.
From the tool's definition Tool name is 'get_my_orders' and description states 'List your open orders on the DEX'. The verb 'list' and the action of retrieving/querying existing order data without modification indicates a read-only operation.
Attacks that exploit this kind of access
The rule that runs get_my_orders 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 get_my_orders, this is the rule to start with:
get_my_orders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every get_my_orders call is checked against it from then on.
Questions about get_my_orders
List your open orders on the DEX. Can filter by token and status. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.
Register the Tempo MCP server in PolicyLayer and add a rule for get_my_orders: 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.
get_my_orders 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_my_orders 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_my_orders. 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_my_orders 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.
This server
Across the catalogue