AI agents invoke ot_make_wish 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 an action in a game world (making a wish at a well) that produces uncertain side effects determined by the system. Although it doesn't delete data or move money, it runs an operation whose effects depend on arguments (the wish text) and system state, fitting the Execute category. The outcome uncertainty elevates severity above a simple Write operation.
From the tool's definition 'Make your wish at the Well at Eldenmoor' and 'outcome is uncertain' and 'Narrate the ending based on the outcome returned' indicate the tool triggers an external operation with unpredictable game-state effects.
Attacks that exploit this kind of access
Make your wish at the Well at Eldenmoor. Only available after reaching the Well. The outcome is uncertain. State your wish clearly. Narrate the ending based on the outcome returned. 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_make_wish: 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_make_wish 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_make_wish 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_make_wish. 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_make_wish 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 →