Get technical analysis indicators for an NZX company. SMA-50/100/200, RSI-14, golden/death cross, distance from 52-week high/low, volume ratios. Use for trading signals, momentum analysis, and technical screening.
AI agents call get_technical_signals to retrieve information from NZXplorer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ticker | string | Yes | NZX ticker symbol (e.g. "AIR", "FPH", "MEL") |
Parameters from the server's own tool schema.
While the tool enables financial decision-making through technical trading signals and could influence high-value investment decisions, it performs no write, execute, or destructive operations. It only retrieves and computes read-only technical indicators.
From the tool's definition Tool provides read-only access to technical analysis indicators: SMA-50/100/200, RSI-14, golden/death cross, distance from 52-week high/low, volume ratios.
Attacks that exploit this kind of access
Get technical analysis indicators for an NZX company. SMA-50/100/200, RSI-14, golden/death cross, distance from 52-week high/low, volume ratios. Use for trading signals, momentum analysis, and technical screening. It is categorised as a Read tool in the NZXplorer MCP Server MCP Server, which means it retrieves data without modifying state.
get_technical_signals accepts 1 parameter: ticker. Required: ticker. The full parameter table on this page comes from the server's own tool schema.
Register the NZXplorer MCP Server MCP server in PolicyLayer and add a rule for get_technical_signals: 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 NZXplorer MCP Server. Nothing to install.
get_technical_signals 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_technical_signals 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_technical_signals. 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_technical_signals is provided by the NZXplorer MCP Server MCP server (mambaventures/nzxplorer-mcp-server). 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 →