MCP

Safety model

How MCP tools stay inside your limits.

Every tool calls the same service layer as REST, with the same scopes and rate limits.
No tool can loosen a limit: update_policy and deploy_squad reuse the REST validation, so loosening returns policy_loosening_rejected and unenforced fields return field_not_enforced.
place_order and retire_squad are marked destructive, so clients ask before running them.
Write tools take an optional idempotency_key; one is generated per call if omitted.

Last updated October 11, 2026

Wisp runs in a sandbox today: paper trading on live market data. Experimental software, not financial advice.