AI agents call line_time_forecast to retrieve information from Mcp Otle without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries or computes estimated data (wait time forecasts) without creating, modifying, deleting, or executing operations. It is informational only, making it a Read category risk. Severity is low because misuse (e.g., providing inaccurate wait time predictions) has minimal blast radius—users receive unhelpful information but no financial, operational, or data integrity harm occurs.
From the tool's definition Tool performs forecasting/prediction using ML algorithms to 'estimate Chipotle line wait times' — a data retrieval and analysis operation with no side effects, no data modification, and no execution of external operations.
Attacks that exploit this kind of access
ML-powered burrito congestion prediction. Uses advanced algorithms to estimate Chipotle line wait times. It is categorised as a Read tool in the Mcp Otle MCP Server, which means it retrieves data without modifying state.
Register the Mcp Otle MCP server in PolicyLayer and add a rule for line_time_forecast: 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 Mcp Otle. Nothing to install.
line_time_forecast 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 line_time_forecast 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 line_time_forecast. 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.
line_time_forecast is provided by the Mcp Otle MCP server (yoshisaurus/mcp-otle). 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 →