スイング高値・安値（ZigZag 相当）を検出する。
AI agents call mt5_swing_points 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 detects/identifies swing high and low points in market data, equivalent to a ZigZag indicator calculation. It is purely a read/query operation retrieving technical analysis data with no side effects on trades or account state.
From the tool's definition スイング高値・安値（ZigZag 相当）を検出する — 'detect swing highs and lows (ZigZag equivalent)'
Attacks that exploit this kind of access
スイング高値・安値（ZigZag 相当）を検出する。. 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_swing_points: 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_swing_points 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_swing_points 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_swing_points. 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_swing_points 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 →