Statistically validated leading indicator signals evaluated against live supply chain data. Each signal is a Granger-causal relationship tested at p<=0.01 with directional accuracy >=55%. Signals predict commodity price movements, manufacturing shifts, and macroeconomic changes 1 week to 6 months...
Part of the Supply Chain Intelligence server.
Free to start. No card required.
AI agents call get_predictive_signals to retrieve information from Supply Chain Intelligence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_predictive_signals only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_predictive_signals": {}
}
}See the full Supply Chain Intelligence policy for all 31 tools.
These attack patterns abuse exactly the kind of access get_predictive_signals gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Statistically validated leading indicator signals evaluated against live supply chain data. Each signal is a Granger-causal relationship tested at p<=0.01 with directional accuracy >=55%. Signals predict commodity price movements, manufacturing shifts, and macroeconomic changes 1 week to 6 months ahead. Returns ACTIVE (threshold crossed — act now), WATCH (approaching threshold — prepare), or CLEAR status for each signal. 58 signals across 3 tiers organized by predictor group (GDI pillars, SMI regions, cross-index spreads). Used by commodity traders for forward-looking positioning, procurement teams for buy/defer timing, and hedge funds for alternative data signals.. It is categorised as a Read tool in the Supply Chain Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Supply Chain Intelligence MCP server in PolicyLayer and add a rule for get_predictive_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 Supply Chain Intelligence. Nothing to install.
get_predictive_signals 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_predictive_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 get_predictive_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.
get_predictive_signals is provided by the Supply Chain Intelligence MCP server (https://supplymaven.com/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 31 Supply Chain Intelligence 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.