Get director appointment, resignation, and retirement events for an NZX company. Shows board composition changes over time with dates and reasons.
AI agents call get_board_changes 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 |
|---|---|---|---|
to | string | — | End date YYYY-MM-DD |
from | string | — | Start date YYYY-MM-DD |
limit | number | — | Max results (default 50) |
action | string | — | Filter by action type: appointed, resigned, retired, removed, elected, re-elected |
ticker | string | Yes | NZX ticker symbol (e.g., FPH, AIR) |
Parameters from the server's own tool schema.
This tool retrieves and displays historical information about board composition changes (appointments, resignations, retirements) for NZX-listed companies. It has no side effects—no data is created, modified, deleted, or overwritten. No code is executed, and no financial transactions are triggered.
From the tool's definition The tool description explicitly states it 'Get[s] director appointment, resignation, and retirement events' and 'Shows board composition changes over time.' These are pure data retrieval operations with no modification, deletion, or execution of external…
Attacks that exploit this kind of access
Get director appointment, resignation, and retirement events for an NZX company. Shows board composition changes over time with dates and reasons. It is categorised as a Read tool in the NZXplorer MCP Server MCP Server, which means it retrieves data without modifying state.
get_board_changes accepts 5 parameters: to, from, limit, action, 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_board_changes: 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_board_changes 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_board_changes 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_board_changes. 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_board_changes 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 →