Get the last error from MT5 terminal.
AI agents call get_last_error 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 queries and retrieves error information from the MT5 terminal without modifying, executing operations on, or destructively affecting any data or trading positions. It is purely informational/diagnostic in nature, fitting the Read category. Severity is low because misuse (e.g., querying error state repeatedly) poses minimal risk compared to trading operations on this server.
From the tool's definition Tool name 'get_last_error' and description 'Get the last error from MT5 terminal' indicate retrieval of error state information with no side effects.
Attacks that exploit this kind of access
Get the last error from MT5 terminal. 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 get_last_error: 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.
get_last_error 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_last_error 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_last_error. 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_last_error is provided by the MetaTrader 5 MCP Server MCP server (jorgearturoyap-debug/metatrader-5-for-chatgpt-desktop). 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 →