Reported issues for AgentGate
Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to AgentGate.
Most discussed
Agent-identity spine: bind verifiable identity across gate decisions, lens traces, and lore writes
Roadmap: Tier 2 — Unify agent identity across the platform's three observability/control layers (gate, lens, lore), turning the fragmented product suite into one governable control plane and building the durable moat from identity standardization (SPIFFE/WIMSE, OAuth2+RFC-8693).
Why
Agent identity is the 2026 standards battleground: SPIFFE/WIMSE workload identity, OAuth2 client-credentials + RFC-8693 token exchange, Auth0-for-AI-Agents, and NIST's new agent-identity initiatives all sign
Read the thread · 2026-06-22 · closed · 4 comments
MCP tool-call guardrails: per-tool action allow-listing enforced right before execution
Roadmap: Tier 3 — MCP-native tool/action allow-listing gated by agent identity, stamped with OWASP-LLM risk tags. From the agentkitai competitive analysis. Borrowed from: Portkey MCP Gateway, LiteLLM MCP guardrails, Akto AgentGuard.
Why
AgentGate already gates approval requests — now plug tool invocations upstream at the MCP protocol boundary. The wedge: enforce policy on tool calls (not LLM completions), right before execution, where pure LLM-proxies and managed MCP gateways are we
Read the thread · 2026-06-22 · closed · 3 comments
webhooks: dev-mode flag to allow loopback/private webhook destinations
AgentGate's webhook SSRF guard (validateWebhookUrl) rejects loopback/RFC-1918 destinations, so local integrations (e.g. the AgentGate×UCP adapter demo, where AgentGate must deliver a decision webhook to a gate on 127.0.0.1) resort to lvh.me/dist-patching workarounds. Add an explicit, default-OFF dev/test flag to permit private destinations — while STILL blocking cloud-metadata endpoints and non-HTTP(S), so the canonical SSRF vectors stay closed.
Read the thread · 2026-07-05 · closed · 0 comments
docs: per-agent governance guide (virtual keys, budgets, policy scoping)
Split out from the now-complete gateway epic #13 (its only unfinished acceptance item).
The per-agent governance model ships and works, but its docs are scattered — there's no single "governance" overview a new user can read end-to-end. Concepts currently live in:
docs/agent-identity.md— agent credentials + virtual-key bindingdocs/policies.md— policy matcher syntax (but not thescope/agentIds/toolIdsper-agent fields)docs/mcp.md— MCP tool-call guardrails / overrides
**De
Read the thread · 2026-06-25 · closed · 0 comments
Per-agent budgets: tighten soft-cap staleness near the limit (force-refresh + spend-read timeout)
Per-agent budget enforcement (#21) is a deliberately soft guardrail: spend is read from AgentLens and cached 30s, so an agent can overshoot by up to ~30s of spend between the budget check and the next refresh, and the hot-path spend read inherits the shared HTTP client's 30s timeout.
Follow-ups to tighten it
- Force a fresh spend read when projected spend nears the cap (e.g. > 80% of limit), rather than serving the 30s-cached value.
- Pass a shorter timeout to the spend-read `Ag
Read the thread · 2026-06-22 · closed · 0 comments
Dashboard UI for per-agent governance (budgets, virtual keys, policy scopes, overrides)
Follow-up to the #13 gateway work (virtual keys #17, per-agent policy scoping #18, per-agent budgets #20/#21). The governance primitives now exist API-only; they need a dashboard surface.
Scope
- Per-agent budgets: set/clear
monthlyBudgetUsd, view current-month spend (GET /api/agents/:id/spend), and budget-vs-spend per agent. - Virtual keys: show which API keys are bound to which agent (
apiKeys.agentId). - Policy scoping: policies grouped by
scope/agentIds/toolIds; c
Read the thread · 2026-06-22 · closed · 0 comments
Most recent
The remaining reports are on the project's issue tracker.