ティック履歴を取得する。from_date(ISO8601) から count 件。
AI agents call mt5_ticks to retrieve information from MT5 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches historical tick data from MetaTrader 5. It is a read-only data retrieval operation with no side effects on accounts, orders, or market positions.
From the tool's definition ティック履歴を取得する — 'get tick history', retrieves historical tick data from a specified date for a given count
Attacks that exploit this kind of access
ティック履歴を取得する。from_date(ISO8601) から count 件。. It is categorised as a Read tool in the MT5 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MT5 MCP Server MCP server in PolicyLayer and add a rule for mt5_ticks: 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 MT5 MCP Server. Nothing to install.
mt5_ticks 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 mt5_ticks 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 mt5_ticks. 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.
mt5_ticks is provided by the MT5 MCP Server MCP server (junmt/mt5-mcp). 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 →