AI agents call view_menu 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 simply displays menu information without modifying, executing external operations, or affecting any data. It is a straightforward read operation with minimal risk if invoked by an AI agent.
From the tool's definition Tool name 'view_menu' and description 'View the full Chipotle menu' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
View the full Chipotle menu. Start here before ordering. 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 view_menu: 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.
view_menu 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 view_menu 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 view_menu. 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.
view_menu 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 →