Get revenue segment breakdown for an NZX company. Returns operating, geographic, or product segment data including segment revenue, operating profit, and assets (all in NZD thousands). Use when asked about "revenue breakdown", "business segments", "divisions", "product groups", "geographic revenu...
AI agents call get_revenue_segments 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 |
|---|---|---|---|
type | string | — | Segment type filter: operating, geographic, product |
year | string | — | Year or range (e.g. "2025" or "2020-2025") |
limit | number | — | Max results (default 50) |
ticker | string | Yes | NZX ticker symbol (e.g. "FPH", "SKC", "AIR", "FBU") |
Parameters from the server's own tool schema.
This tool retrieves and queries existing financial data about revenue segments for NZX-listed companies. It performs a passive read operation with no side effects—it does not create, modify, delete, or execute any actions. The data returned (revenue breakdown, segment metrics) is informational only.
From the tool's definition Tool description explicitly states it "Returns" data: "segment revenue, operating profit, and assets". The verb "Get" and "Returns" indicate data retrieval with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get revenue segment breakdown for an NZX company. Returns operating, geographic, or product segment data including segment revenue, operating profit, and assets (all in NZD thousands). Use when asked about "revenue breakdown", "business segments", "divisions", "product groups", "geographic revenue", "segment analysis", or "what are the divisions of [company]". It is categorised as a Read tool in the NZXplorer MCP Server MCP Server, which means it retrieves data without modifying state.
get_revenue_segments accepts 4 parameters: type, year, limit, 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_revenue_segments: 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_revenue_segments 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_revenue_segments 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_revenue_segments. 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_revenue_segments 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 →