Skip to main content
Glama
GATE — Live Agent Authority Verification

GATE — Live Agent Authority Verification

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GATE_URLNoGATE Network endpoint
GATE_API_KEYNoProject API key; required for authenticated verification calls
GATE_TIMEOUT_MSNoOptional request timeout in milliseconds

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
gate_verifyA

Verify whether an AI agent currently has a valid delegated authority path from a principal for a requested action. Call immediately before a protected operation, using trusted principal, actor and action context. The verifier evaluates current authority evidence, including upstream revocation and alternative delegation paths, subject to the configured consistency and freshness guarantees. Inspect the returned decision: ALLOW, DENY or UNKNOWN authority. UNKNOWN must not permit the protected action. A standalone verification response does not enforce authorization: the trusted execution boundary must enforce the decision. Live network verification requires a configured GATE endpoint and appropriate credentials. Demo mode is simulated and not production authority.

gate_statusA

Inspect the configured GATE verifier mode and operational status. Use this tool for setup checks and troubleshooting, not to authorize an action. In demo mode, it reports the local simulated authority graph. In network mode, it requests the configured endpoint health information. A healthy response does not prove that an actor has permission to act. Use gate_verify at the trusted effect boundary for authority decisions. If the status request fails, do not assume access is allowed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

gate_verify (authority decision at effect boundary) and gate_status (configuration/health inspection) are explicitly delineated, and both descriptions cross-reference each other to prevent misuse. An agent can unambiguously choose between making an authorization decision and checking setup/health.

Naming Consistency5/5

Both tools use a uniform snake_case verb/noun pattern with a consistent 'gate_' prefix (gate_verify, gate_status). The convention is predictable and scales if more gate operations are added.

Tool Count3/5

Two tools is thin even for a narrowly scoped verification service; the surface is tightly focused but offers no affordances beyond a single decision call and a status probe. It sits at the borderline of minimal but arguably sufficient.

Completeness4/5

The core lifecycle — check readiness, then verify authority at the effect boundary — is covered, including the critical UNKNOWN/deny semantics. Minor gaps remain: no way to inspect delegation chains, revocation evidence, or batch/bulk verification results directly.

Maintenance

ActivityActive
ResponsivenessNo recent community issues