Forecast total store revenue over a future horizon using TimesFM 2.5.
AI agents call forecast_revenue to retrieve information from Shopify Forecast without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data analysis and prediction based on existing store data without creating, modifying, deleting, or executing external operations. It reads historical revenue data and applies a pre-built forecasting model to generate predictions. This is a classic Read operation with no side effects on the store's systems or data.
From the tool's definition Tool name 'forecast_revenue' and description 'Forecast total store revenue over a future horizon' indicate retrieval and analysis of predictive data using an existing model (TimesFM 2.5).
Attacks that exploit this kind of access
Forecast total store revenue over a future horizon using TimesFM 2.5. It is categorised as a Read tool in the Shopify Forecast MCP Server, which means it retrieves data without modifying state.
Register the Shopify Forecast MCP server in PolicyLayer and add a rule for forecast_revenue: 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 Shopify Forecast. Nothing to install.
forecast_revenue 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 forecast_revenue 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 forecast_revenue. 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.
forecast_revenue is provided by the Shopify Forecast MCP server (mcostigliola321/shopify-forecast-mcp). 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 →