Reference

FAQ & limitations

Is CloakPipe open source?

Yes. Everything on these pages is in rohansx/cloakpipe under the MIT licence v0.12 (v0.11.0 had two crates under Apache-2.0). There is no paid edition of the gate, and no feature on these pages needs an account.

Do I need an account or a service?

No. Webhook alerts to your own Slack or Discord v0.13 go straight from the gate to the URL you give it. Hosted alerts and approvals (grouped issues, approval cards, escalation, digests) are an idea we are testing and are not built. v0.14 The gate can file approval requests with an approval broker, but only one you configure; enforcement never depends on it. If you would use them, tell us on the waitlist. The gate is self-hosted by design: it never needs to send arguments, credentials or results anywhere.

Why not just tell the model the rules in the prompt?

Because a prompt is input to the same model an attacker is trying to steer. The manifest and policy are checked by code outside the model, on the call it actually proposed, against values (the task context) the model cannot write. A prompt injection can change what the model asks for; it cannot change what the gate allows.

Does it slow tool calls down?

The contract and Cedar checks are fast: the test suite asserts p99 under 5ms on the example manifest, with 2ms as the target. Each decision also writes and signs a ledger entry in SQLite before the call is forwarded. Anchoring runs on a background thread, off the request path. Tool calls usually take far longer than either.

What happens when the gate refuses a call?

The agent gets a JSON-RPC error (-32001) with a reason such as scope_mismatch or undeclared_tool, the tool never sees the call, and the refusal is a signed ledger entry. Most hosts pass the error back to the model as a failed tool call. See MCP tool gate.

Can I try it without blocking anything?

Yes: --mode shadow forwards every call and records what enforce mode would have decided. See shadow mode.

Do I have to write Cedar?

No. A manifest without policy: is enforced on its own: closed tool and argument lists, value rules, one_of_context, side-effect tracking and conditional approval. Add a Cedar policy when you need rate limits, time windows or rules over the task.

Where did evaluation import and release sign-off go?

CloakPipe used to sign off agent releases from evaluation results. That is out of scope now: the product is the gate on tool calls. The old commands are behind a source-only cargo feature that published binaries do not include, and they will be removed. The old manifest format still works for one more release; see the legacy format.

What about PII?

The binary can pseudonymize personal data in allowed calls (mcp-proxy --transform pii) and in LLM traffic (cloakpipe start). It is optional and off by default; the gate never rewrites an allowed call unless you ask it to.

Known limitations

  • One server per gate, stdio only, up to v0.12.0. v0.13 MCP over HTTP on both sides, several stdio servers behind one gate, and tools/list pinning with drift detection are in v0.13.0. See MCP tool gate. Still Roadmap: SSE response streams to HTTP agents, and HTTP servers behind --server.
  • tools/list is not pinned up to v0.12.0. A server that changes its tool descriptions is not detected there. v0.13 cloakpipe tools pin and --tools-lock hide and refuse a changed tool.
  • Static task context. --task-context is read once at start-up; run one gate per task when tasks change. A per-task channel from the orchestrator is Roadmap.
  • Approvals need a broker you run, or cloakpipe approve by hand. Up to v0.13.0, nothing collected the approval or delivered the receipt: a human ran cloakpipe approve. v0.14 The gate files approval requests with an approval broker (--approvals-url) and verifies the receipts it hands back; the protocol is open, so you can run your own. See Approvals. Roadmap CloakPipe Cloud as a hosted broker with approval cards in Slack is coming soon, not deployed yet; approving with an edit (changing an argument) is not built.
  • No alerts up to v0.12.0. The ledger and stderr are the record there. v0.13 Signed webhooks (Slack, Discord), OpenTelemetry spans and a JSONL event log; see Alerts & events. Hosted alerts are Roadmap.
  • The LLM proxy does not gate tool calls. cloakpipe start transforms PII only. Roadmap
  • Counters count calls, not amounts. Money budgets are Roadmap.
  • Keys are files. KMS and HSM support and in-ledger key rotation are Roadmap. See Keys.
  • Verifier gaps. TSA revocation (CRL/OCSP) and Rekor log consistency are not checked. See Evidence & verification.

Still stuck?

Email rohan@cloakpipe.co or open an issue on GitHub.