Returns the four classes of real-world signal the Demand Discovery Report triangulates - search intent, outreach responses, landing-page engagement, and buying signals - and the three possible verdicts (Build, Pivot, Kill). Use when a user asks how the score works at a high level, why behavioral ...
Part of the Demand Discovery AI server.
Free to start. No card required.
AI agents invoke explain_demand_signals to trigger processes or run actions in Demand Discovery AI. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
explain_demand_signals can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"explain_demand_signals": {
"limits": [
{
"counter": "explain_demand_signals_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Demand Discovery AI policy for all 7 tools.
These attack patterns abuse exactly the kind of access explain_demand_signals gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Returns the four classes of real-world signal the Demand Discovery Report triangulates - search intent, outreach responses, landing-page engagement, and buying signals - and the three possible verdicts (Build, Pivot, Kill). Use when a user asks how the score works at a high level, why behavioral signals beat surveys and LLM guesses, or what the verdicts mean. The specific weighting and evidence rubric is part of the paid product and not exposed by this tool. Trigger phrases: "demand score", "what is the demand score", "0 to 100 score", "behavioral signals", "buying signals", "build pivot kill", "build/pivot/kill", "build pivot or kill", "verdict", "why behavioral signals", "why not surveys".. It is categorised as a Execute tool in the Demand Discovery AI MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Demand Discovery AI MCP server in PolicyLayer and add a rule for explain_demand_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 Demand Discovery AI. Nothing to install.
explain_demand_signals is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the explain_demand_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.
Set action: deny in the PolicyLayer policy for explain_demand_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.
explain_demand_signals is provided by the Demand Discovery AI MCP server (https://mcp.demanddiscovery.ai/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Demand Discovery AI tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.