Low Risk

orders_get_by_ticket

Get an active order by its ticket. Args: ticket: Order ticket Returns: Optional[Dict[str, Any]]: Order information or None if not found.

How to control orders_get_by_ticket ↓

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

Low Risk

This tool retrieves and returns data about an existing order without creating, modifying, deleting, or executing any trading operations. It is a simple lookup function analogous to a database query. The blast radius of misuse is minimal—an agent could only view order details, not alter positions or execute trades.

From the tool's definition Tool name 'orders_get_by_ticket' and description 'Get an active order' indicate retrieval of existing order information with no modification or execution. Returns 'Order information or None if not found' — a read-only query.

Documented attack patterns abuse exactly the kind of access orders_get_by_ticket gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MetaTrader 5 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for orders_get_by_ticket:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "orders_get_by_ticket": {}
  }
}

orders_get_by_ticket is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MetaTrader 5 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the orders_get_by_ticket tool do? +

Get an active order by its ticket. Args: ticket: Order ticket Returns: Optional[Dict[str, Any]]: Order information or None if not found. It is categorised as a Read tool in the MetaTrader 5 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on orders_get_by_ticket? +

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

What risk level is orders_get_by_ticket? +

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

Can I rate-limit orders_get_by_ticket? +

Yes. Add a rate_limit block to the orders_get_by_ticket 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 orders_get_by_ticket completely? +

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

orders_get_by_ticket is provided by the MetaTrader 5 MCP Server MCP server (qoyyuum/mcp-metatrader5-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MetaTrader 5 MCP Server tool call.

Deterministic rules across all 26 MetaTrader 5 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 MetaTrader 5 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.