Get stock performance metrics for an NZX company. Returns (1d to 5y), alpha vs NZX50, volatility, 52-week range, market cap. Use for performance comparison and pay-for-performance analysis.
AI agents call get_performance 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 |
Parameters from the server's own tool schema.
This is a read-only query tool that retrieves and presents financial market data for analysis purposes. It has no ability to modify data, execute trades, delete information, or create financial obligations. The blast radius of misuse is minimal—an AI agent could only access or report existing public market information.
From the tool's definition Tool retrieves historical stock performance metrics (1d to 5y returns, alpha, volatility, 52-week range, market cap) with no modification or execution capabilities. The description explicitly states 'Get' and 'Returns', indicating data retrieval only.
Attacks that exploit this kind of access
Get stock performance metrics for an NZX company. Returns (1d to 5y), alpha vs NZX50, volatility, 52-week range, market cap. Use for performance comparison and pay-for-performance analysis. It is categorised as a Read tool in the NZXplorer MCP Server MCP Server, which means it retrieves data without modifying state.
get_performance 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_performance: 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_performance 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_performance 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_performance. 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_performance 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 →