Skip to main content
Glama

Declared-vs-Enforced Agent Access Verification

Server Details

Compares declared agent access against actual enforcement per identity class, with drift watch.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
ChatGPT
–
Claude
–

TDQS

B3/5.0

Scored across 4 tools

Disambiguation4/5

The four tools have distinguishable scopes: access_probe is a one-time declared-vs-enforced check on an arbitrary path, while drift_run re-probes already-enrolled targets, and drift_targets/drift_remove manage the enrollment list. The main ambiguity is between access_probe and drift_run (both perform probing), and it is unclear whether access_probe also enrolls a target, since removal/listing imply enrollment exists but no explicit enroll tool is present.

Naming Consistency4/5

All names use snake_case and a predictable <domain>_<action> structure, with three tools sharing the drift_ prefix. The only deviation is access_probe, which is an outlier prefix and reads noun_verb rather than the domain_action pattern of the drift_ family.

Tool Count4/5

Four tools is a tight, well-scoped set for a narrow verification/drift-checking server, and each tool maps to a distinct operation. It is on the thin side — the absence of an enrollment or history-retrieval tool suggests the count reflects a deliberately minimal surface rather than a fully rounded one.

Completeness3/5

The lifecycle is incomplete: targets can be listed and removed, and drift is recorded, but there is no explicit enrollment/create tool and no tool to read back recorded drift events or history, leaving agents unable to retrieve the drift data they generate. Core probe workflows are covered, but these gaps will force workarounds.

Available Tools

4 tools
access_probeCInspect

Pre-flight declared-vs-enforced probe of one target path (one-time grant; the $0.01 x402 rail is the HTTP /probe endpoint).

Inputs: base_url (required), path, signed, fixture, +1 more.

drift_removeCInspect

Remove one enrolled drift-watch target (records no drift event).

Inputs: target_id (required).

drift_runBInspect

Re-probe one enrolled target now and record two-sided drift (manual runs metered: 1/min/target).

Inputs: target_id (required).

drift_targetsBInspect

List your enrolled drift-watch targets.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only comparison of Stripe active entitlements against an application's effective access snapshots, returning matched, mismatch, or unknown results for agent-driven diagnostics.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Provides policy-based access control, incident tracking, and compliance monitoring to govern AI agent behavior. It enables organizations to enforce security rules and maintain audit trails by validating agent actions against trust levels and pattern-based policies.
      6
      1
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources