Overrides with an agent

The registered override tools manage proxy and credential overrides. Values replace caller values with the same key. Among matching records, higher-priority overrides win.

Call get_guide with guide_key: "override-creation" before the first create.

Call order

1. Call create_proxy_override.
   • Required: clientId, proxyId, overrideActive, overrideMode.
   • Optional: overrideHeaders, overrideQueryParams, overrideData, effect, priority, methods, notes, alerts, path, headers, query, body, token, variables.
2. Keep the returned override sKey.
3. Call get_proxy_override(clientId, proxyId, overrideId) to verify the maps.

list_proxy_overrides requires clientId and proxyId. update_proxy_override also requires overrideId; other arguments are optional. Credential equivalents are list_credential_overrides, get_credential_override, create_credential_override, and update_credential_override.

Example

{
  "tool": "create_proxy_override",
  "arguments": {
    "clientId": "b3a1c7d2-5e44-4f0a-9c1e-7d2f8a6b1c90",
    "proxyId": "5d8a1c30-4e72-4b19-8f6a-0c3d9e7b1a25",
    "overrideActive": true,
    "overrideMode": "all",
    "overrideHeaders": {
      "X-Source": "requestrocket"
    }
  }
}

The target receives X-Source: requestrocket, replacing a caller header with the same name.

Next