This record as markdown: /tools/af7007-mcp-trader/get-version.md
What get_version does on MCP Trader Server
AI agents call get_version to retrieve information from MCP Trader Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_version is rated Low
This tool merely fetches metadata about the MetaTrader 5 installation. It has no side effects, does not execute trades, modify data, or delete anything. It is a read-only informational query with minimal security impact if misused by an AI agent.
From the tool's definition Tool name 'get_version' and description 'Get the MetaTrader 5 version' indicate a simple query operation that retrieves version information without modifying or executing any operations.
Attacks that exploit this kind of access
The rule that runs get_version safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Trader Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_version, this is the rule to start with:
get_version 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 MCP Trader Server, apply this rule, and every get_version call is checked against it from then on.
Questions about get_version
Get the MetaTrader 5 version. It is categorised as a Read tool in the MCP Trader Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Trader Server MCP server in PolicyLayer and add a rule for get_version: 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 MCP Trader Server. Nothing to install.
get_version 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_version 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_version. 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_version is provided by the MCP Trader Server MCP server (af7007/mcp-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Trader Server, and thousands of servers like it.
This server
Across the catalogue