Get detailed profile for a specific director by slug. Includes biography, board seats, compensation, share trades.
AI agents call get_director_detail 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 |
|---|---|---|---|
slug | string | Yes | Director slug (e.g. "dame-therese-walsh") |
include | string | — | Comma-separated: trades, remuneration, exec_comp |
Parameters from the server's own tool schema.
This tool retrieves and queries director information (biography, board positions, compensation, historical share trades) with no side effects. It does not create, modify, delete, execute code, or perform financial transactions. The data retrieved about director compensation and past trades is historical and informational, not an action that moves money or commits obligations. Classification as Read is appropriate.
From the tool's definition Tool name 'get_director_detail' and description 'Get detailed profile for a specific director by slug. Includes biography, board seats, compensation, share trades' indicate data retrieval only.
Attacks that exploit this kind of access
Get detailed profile for a specific director by slug. Includes biography, board seats, compensation, share trades. It is categorised as a Read tool in the NZXplorer MCP Server MCP Server, which means it retrieves data without modifying state.
get_director_detail accepts 2 parameters: slug, include. Required: slug. 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_director_detail: 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_director_detail 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_director_detail 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_director_detail. 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_director_detail 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 →