Get a market summary for a state: total active listings, score distribution,
AI agents call get_market_summary to retrieve information from NDI-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregated market data (listings count, score distributions) for informational purposes. It has no side effects, does not modify data, and poses minimal risk if misused by an agent—the worst outcome would be retrieving market data the agent shouldn't see, a confidentiality concern rather than a safety risk. Classification as Read is appropriate.
From the tool's definition Tool name 'get_market_summary' and description 'Get a market summary for a state: total active listings, score distribution' indicate data retrieval only.
Attacks that exploit this kind of access
Get a market summary for a state: total active listings, score distribution,. It is categorised as a Read tool in the NDI-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the NDI-MCP-Server MCP server in PolicyLayer and add a rule for get_market_summary: 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 NDI-MCP-Server. Nothing to install.
get_market_summary 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_market_summary 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_market_summary. 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_market_summary is provided by the NDI-MCP-Server MCP server (CREIntel/ndi-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 →