get_directors

Search NZX company directors. Returns name, bio, board seats. Filter by company or search by name.

Server NZXplorer MCP Server mambaventures/nzxplorer-mcp-server
Category Read
Risk class Low
Parameters 40 required

What get_directors does on NZXplorer MCP Server

AI agents call get_directors 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.

ParameterTypeRequiredDescription
limit number Max results
search string Search director name
company string Filter by company ticker
current boolean Only current directors (default true)

Parameters from the server's own tool schema.

Why get_directors needs a policy

The tool retrieves publicly available director information from the NZX database. It has no side effects, cannot modify data, execute code, delete records, or trigger financial transactions. The blast radius of misuse is minimal—an AI agent could only retrieve director details that are already public market data.

From the tool's definition Tool performs 'Search' and 'Returns' operations (name, bio, board seats) with filtering capabilities—classic read-only data retrieval with no modification or execution of external commands.

Questions about get_directors

What does the get_directors tool do? +

Search NZX company directors. Returns name, bio, board seats. Filter by company or search by name. It is categorised as a Read tool in the NZXplorer MCP Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_directors accept? +

get_directors accepts 4 parameters: limit, search, company, current. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_directors? +

Register the NZXplorer MCP Server MCP server in PolicyLayer and add a rule for get_directors: 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.

What risk level is get_directors? +

get_directors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_directors? +

Yes. Add a rate_limit block to the get_directors 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.

How do I block get_directors completely? +

Set action: deny in the PolicyLayer policy for get_directors. 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.

What MCP server provides get_directors? +

get_directors 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.