Get the sell probability signal for a listed property — the likelihood it transacts
AI agents call get_sell_signal 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 queries and returns analytical data (a probability signal) about a property. It performs no reversible creation/modification, irreversible deletion, code execution, or financial transactions. It is a straightforward data retrieval operation with no side effects, fitting the Read category.
From the tool's definition Tool retrieves 'sell probability signal' and 'likelihood it transacts' for a property—a read-only query of predictive data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get the sell probability signal for a listed property — the likelihood it transacts. 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_sell_signal: 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_sell_signal 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_sell_signal 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_sell_signal. 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_sell_signal 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 →