Hit the trail for 3 days. Always costs food and may affect health — plan supplies before calling. Costs: easy=-6 food, +9hp each; steady=-9 food, 0hp change; hard=-12 food, -21hp each, -12hp pet. Random events add further gains/losses on top. Narrate what happens to the human dramatically.
AI agents invoke ot_travel to trigger actions in Ttt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a multi-step game action with side effects: it consumes resources (food), modifies health values, applies random events, and generates narrative output. It is not a simple read; it alters game state in ways that depend on arguments and random outcomes.
From the tool's definition 'Hit the trail for 3 days. Always costs food and may affect health — plan supplies before calling.' Random events trigger further state changes.
Attacks that exploit this kind of access
Hit the trail for 3 days. Always costs food and may affect health — plan supplies before calling. Costs: easy=-6 food, +9hp each; steady=-9 food, 0hp change; hard=-12 food, -21hp each, -12hp pet. Random events add further gains/losses on top. Narrate what happens to the human dramatically. It is categorised as a Execute tool in the Ttt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ttt MCP server in PolicyLayer and add a rule for ot_travel: 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 Ttt. Nothing to install.
ot_travel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ot_travel 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 ot_travel. 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.
ot_travel is provided by the Ttt MCP server (srmtech-git/mcparcade). 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 →