AI agents use post_gym_macro_mode to create or update resources in Mcp Otle — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Otle environment.
This tool creates or modifies an order configuration (a burrito) based on workout input, which is a reversible Write operation. There are no side effects beyond order simulation/suggestion, no financial transactions, no destructive operations, and no code execution. The humorous 'Gains-as-a-Service' framing and the fact this is part of a Chipotle ordering simulator (not a real system) further indicate low severity.
From the tool's definition The tool 'automatically configures' a burrito order, which is a create/modify operation similar to other build/customize operations on this server (build_entree, customize_order).
Attacks that exploit this kind of access
Automatically configures a nutritionally optimized burrito based on your workout. Gains-as-a-Service. It is categorised as a Write tool in the Mcp Otle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Otle MCP server in PolicyLayer and add a rule for post_gym_macro_mode: 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.
post_gym_macro_mode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the post_gym_macro_mode 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 post_gym_macro_mode. 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.
post_gym_macro_mode 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 →