get_market_signals

Get the Market Intelligence Feed — a unified stream of all NZX market events. Returns 13 signal types: insider trades, capital raises, dividends, earnings releases, AGM results, director changes, governance score changes, technical signals (golden/death cross, RSI extremes), credit rating changes...

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

What get_market_signals does on NZXplorer MCP Server

AI agents call get_market_signals 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
days number Number of days to look back (default 180, use 7 for "this week", 1 for "today")
type string Comma-separated signal types: insider_trade, capital_raise, dividend, earnings, agm_result, director_change, grs_change, technical_signal, credit_rating, audit_
limit number Max results (default 50)
sector string Filter by sector (e.g. "Energy", "Healthcare")
ticker string Filter by company ticker (e.g. "AIR", "MEL")
significance string Filter by significance: high, medium, low

Parameters from the server's own tool schema.

Why get_market_signals needs a policy

This tool retrieves and aggregates market data and event streams from the NZX. It performs no write operations, does not execute external code or commands, and cannot modify or delete data. The 'signal' terminology refers to data points being returned, not executable actions. Even with access to sensitive data like insider trades, the tool itself is read-only with no capacity for misuse beyond information exposure.

From the tool's definition Tool description describes data retrieval operations: 'Returns 13 signal types' including 'insider trades, capital raises, dividends, earnings releases, AGM results, director changes' and 'technical signals'.

Questions about get_market_signals

What does the get_market_signals tool do? +

Get the Market Intelligence Feed — a unified stream of all NZX market events. Returns 13 signal types: insider trades, capital raises, dividends, earnings releases, AGM results, director changes, governance score changes, technical signals (golden/death cross, RSI extremes), credit rating changes, auditor changes, takeover/M&A activity, board events, and composite signals (multi-signal patterns like insider selling + earnings miss, director exodus, governance deterioration). Use this when asked "what happened on the NZX today/this week?", "any recent insider trades?", "golden crosses?", "credit rating changes?", "composite signals?", "market activity for AIR", or any question about recent NZX events. 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_market_signals accept? +

get_market_signals accepts 6 parameters: days, type, limit, sector, ticker, significance. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_market_signals? +

Register the NZXplorer MCP Server MCP server in PolicyLayer and add a rule for get_market_signals: 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_market_signals? +

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

Can I rate-limit get_market_signals? +

Yes. Add a rate_limit block to the get_market_signals 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_market_signals completely? +

Set action: deny in the PolicyLayer policy for get_market_signals. 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_market_signals? +

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