Start a new Pokemon battle. Only one battle can be active at a time — starting a new one replaces any existing battle. Each Pokemon gets 4 moves drawn from their move pool. The faster Pokemon acts first.
AI agents invoke start_battle to trigger actions in Pokemon MCP Server. 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 battle simulation system with side effects that depend on arguments (which Pokemon participate). While battles are reversible (unlike deletion), the tool initiates external operations (turn-based combat logic, move selection, state management) whose effects cascade through the system.
From the tool's definition Tool description states it 'Start[s] a new Pokemon battle' and 'starting a new one replaces any existing battle', indicating it triggers a complex state-changing operation with multiple side effects including move assignment, turn order determination, and…
Attacks that exploit this kind of access
Start a new Pokemon battle. Only one battle can be active at a time — starting a new one replaces any existing battle. Each Pokemon gets 4 moves drawn from their move pool. The faster Pokemon acts first. It is categorised as a Execute tool in the Pokemon MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pokemon MCP Server MCP server in PolicyLayer and add a rule for start_battle: 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 Pokemon MCP Server. Nothing to install.
start_battle 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 start_battle 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 start_battle. 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.
start_battle is provided by the Pokemon MCP Server MCP server (thesidshah/pokemon-mcp). 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 →