What it means
Every mutating tool on the Aeris MCP surface requires anidempotency_key so a network retry never accidentally applies the same change twice. If the key is absent, the request is rejected before any state change happens.
How to fix
- Mint a client-side key (UUIDv4 or any stable per-intent string) and pass it with the call.
- Reuse the same key when retrying a call whose outcome is unknown — Aeris will return the original result rather than repeat the action.
- Mint a fresh key for each new intent, not once per session.
Response envelope
Related
IDEMPOTENCY_CONFLICT— the key was provided but reused with a different payload.INVALID_INPUT— the other 422 shape.