Get an active order by its 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.
This tool retrieves order data by ticket identifier. While classified as Read (no side effects), the severity is elevated to medium because the retrieved information (active order details) could include sensitive trading positions, account exposure, and financial strategy details that could be exploited if an AI agent misuses access to retrieve and exfiltrate this data at scale or without authorization.
From the tool's definition Tool name 'orders_get_by_ticket' and description 'Get an active order by its ticket' indicate a retrieval operation that queries order information without modifying state.
Attacks that exploit this kind of access
Get an active order by its ticket. It is categorised as a Read tool in the MetaTrader 5 MCP Server MCP Server, which means it retrieves data without modifying state.
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.
orders_get_by_ticket 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 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.
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.
orders_get_by_ticket is provided by the MetaTrader 5 MCP Server MCP server (sameerasulakshana/mcpmt5). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →