Skip to content
MCP server

Odile Gate

By odilelabsAll Odile Labs servers

Stop AI agents looping on or overreaching your API: app keys, approvals, safe retries, audit log

First seen 20 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

1
Directories
Collected by InvokeRank
20
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
gate_add_appGive one app its own key and the calls it may make. Routes are rules like "GET /orders/:id", "POST /orders", "GET /users/{user}/orders" (per-user), or example calls like "GET /orders/42", which become rules. Returns the app key (shown once).Changes data
gate_add_approverCreate an approver key for the person who approves held actions (shown once). Give it to that person, never to an agent: once a project has an approver, the admin key can no longer approve.Changes data
gate_auditThe most recent calls through the gateway (time, app, matched route, status, reason, duration), newest first, with totals by status and refusal reason. Gate never stores bodies, query values or headers.Read-only
gate_audit_proofRead chained audit rows and their anchors with an HMAC-SHA256 signature. Old rows before genesis are excluded; store_audit=false projects have no chain. Row-id range, up to 10,000 rows per page; follow next_from.Read-only
gate_audit_verifyRecompute a pasted export chain and project signature; returns intact or broken_at (one-based row position). Does not approve actions or change permissions.Read-only
gate_check_setupRead actual Gate protection settings before giving an integration production access. Reports observe-only mode, writes without mandatory runs, missing user-token configuration, wildcard grants and approval separation, with evidence, exact remedies and explicit limits. Sends no upstream requests, changes no settings and uses no gateway quota. Configuration-only: not a security certificate or runtime enforcement test.Read-only
gate_create_projectPut Odile Gate in front of an existing HTTPS API. Returns project_id, admin_key (shown once) and the gateway base URL apps call instead of the API.Changes data
gate_create_runGate Actions: give one agent session narrow, expiring permission. Actions are rules with {placeholders} bound by scope (e.g. "PATCH /customers/{customer}/tickets/:id" with scope {"customer":"A"}), each with an optional max and approval. Returns a run token (shown once) the agent sends as x-odile-run with its app key. Writes in a run need an Idempotency-Key. Give a write a check ("GET /bookings?idempotency_key={key}") and the agent can settle a lost answer with POST /g/<id>/_gate/recover.Changes data
gate_delegate_runHand a narrower run to another active app in the same project. Uses the parent app key and run token, never the admin key. Scope, expiry, approvals and ancestor budgets stay enforced; maximum depth five.Changes data
gate_explain_refusalWhat a Gate refusal means and how to fix it, from the x-gate-refused header value (e.g. route_not_allowed).Read-only
gate_learn_suggestionsRead normalized routes and a suggested per-minute limit from an admin-enabled, time-boxed learning session. Records only method, normalized path templates and counts per minute; no query values, raw ids, headers or bodies. Never enables learning or applies rules.Read-only
gate_list_actionsActions waiting for approval (or in another state), with the exact call. Approving is done by a person in the dashboard, not by a tool.Read-only
gate_list_appsThe project's apps with their allowed calls, limits and state.Read-only
gate_metricsRead last-24-hour stored call counts by HTTP status and reason, measured duration through response headers (including upstream wait), and separate current-month gateway usage. Project admin only. Audit may be partial: invalid-key sampling and audit-off periods are disclosed. No upstream requests, quota use or policy changes; not a health certificate or performance guarantee.Read-only
gate_run_timelineRead call metadata, approvals and approver names, recovery outcomes and delegated children; no bodies or query values.Read-only
gate_run_treeRead a run and its delegated descendants without tokens.Read-only
gate_set_app_runsMake an app need a run: "writes" (every write needs x-odile-run), "all" (every call), or "off".Changes data
gate_set_responseOpt-in JSON response redaction: return only explicit JSON Pointer paths, e.g. /id and /items/*/name. * matches one segment; selecting a container allows its whole subtree. Applies to every upstream response for this app, including errors. Maximum 1 MiB and 5 seconds to read; invalid/non-JSON responses are withheld. No bodies are stored. A withheld reply never reverses an upstream write. null disables filtering. Free and Pro.Changes data
gate_sync_declarativeMake a Gate project match an odile.yaml: creates the project (if no project_id) and missing apps and approvers, applies run mode, loop and learning settings and alerts. Never revokes or deletes; differences it cannot apply (an app's routes or rate limit) come back as drift. dry_run lists the steps without changing anything. New keys are shown once.Changes data
gate_validate_configParse and check a declarative Gate config (apps, routes, rate limits, run mode, plugins, alerts, approvers) without changing anything. Returns errors with their path, warnings, and the normalized config.Read-only

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryOdile Gate-20 Oct 2026