AI agents invoke bs_new_game 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 initialization sequence that sets up game state, places entities (fleets), and establishes turn order. While the action itself is reversible (a new game can be started to replace the old), it is an Execute-category tool because it triggers complex external operations with effects that unfold based on player interactions and argument choices.
From the tool's definition Tool name 'bs_new_game' paired with description indicating game state initialization ('Start a new Battleship game', 'Both fleets are placed secretly', 'Pirates fire first').
Attacks that exploit this kind of access
Start a new Battleship game: Pirates vs the Royal Navy. Both fleets are placed secretly. Each ship carries hidden cargo revealed only when sunk. Pirates fire first. 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 bs_new_game: 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.
bs_new_game 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 bs_new_game 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 bs_new_game. 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.
bs_new_game 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 →