AI agents invoke ot_use_medicine 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 game action with side effects—consuming a limited resource (medicine dose) and modifying party member health state. It is not merely Read (no data retrieval), not Write in the reversible sense (consumables are typically one-way), and not Destructive (health restoration is not irreversible data loss).
From the tool's definition Tool description states 'Use one dose of medicine on a party member. Restores significant health.' This indicates an action that modifies game state and triggers external logic (applying a consumable item with quantified effects).
Attacks that exploit this kind of access
Use one dose of medicine on a party member. Restores significant health. Use it when someone is struggling or worse. 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_use_medicine: 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_use_medicine 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_use_medicine 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_use_medicine. 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_use_medicine 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.
ot_use_medicine is one line of Ttt's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →