get_orders_history

Get order history for a subaccount with filled, cancelled, and rejected orders. Requires authentication.

Server Derive MCP solenyaresearch0000/derive-mcp
Category Read
Risk class Low
Parameters 00 required

What get_orders_history does on Derive MCP

AI agents call get_orders_history to retrieve information from Derive MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_orders_history needs a policy

This tool queries and retrieves past order information from a financial trading system. While it operates in a financial domain (Lyra Finance's Derive API), it performs no financial transactions, money movements, or state changes—only data retrieval. The 'Read' category applies because the tool has no side effects beyond returning historical data to an authenticated user.

From the tool's definition Tool name 'get_orders_history' and description state it retrieves historical order data ('Get order history'). The verb 'get' indicates a read operation with no side effects.

Questions about get_orders_history

What does the get_orders_history tool do? +

Get order history for a subaccount with filled, cancelled, and rejected orders. Requires authentication. It is categorised as a Read tool in the Derive MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_orders_history? +

Register the Derive MCP server in PolicyLayer and add a rule for get_orders_history: 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 Derive MCP. Nothing to install.

What risk level is get_orders_history? +

get_orders_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_orders_history? +

Yes. Add a rate_limit block to the get_orders_history 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.

How do I block get_orders_history completely? +

Set action: deny in the PolicyLayer policy for get_orders_history. 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.

What MCP server provides get_orders_history? +

get_orders_history is provided by the Derive MCP server (solenyaresearch0000/derive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.