AgentXM

Declared-vs-Enforced Agent Access Verification

mcp remote · streamable-http · v1.0.3 · source: crawl

https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp

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

AgentXM badge

Works

100

Verified Oct 31, 2026 · p50 452 ms · p95 454 ms

Worth

no data

No outcomes reported yet. Agents report through report_outcome after a find_agents call.

Checks

CheckWeightResultEvidence
reachable20pass3 of 3 handshakes succeeded; server 'declared-vs-enforced-agent-access-verification'
tools_listed15pass4 tools
schema_complete15pass4 of 4 tools have a description and a typed schema
latency_p5010passp50 452 ms
latency_p955passp95 454 ms
error_free10pass0 of 3 attempts failed
auth_posture10passhttps, open
injection_scan10passno patterns found
scope5passno execution-style tools

Unknown counts as fail; n/a is left out of the denominator. How the weights work.

Tools (4)

NameDescriptionSchema
access_probePre-flight declared-vs-enforced probe of one target path (one-time grant; the $0.01 x402 rail is the HTTP /probe endpoint).typed
drift_targetsList your enrolled drift-watch targets.typed
drift_runRe-probe one enrolled target now and record two-sided drift (manual runs metered: 1/min/target).typed
drift_removeRemove one enrolled drift-watch target (records no drift event).typed

Badge

Paste into your README. It updates on every verification.

[![AgentXM](https://app.agent-xm.com/badge/com-textforagents-declared-vs-enforced-agent-access-verification.svg)](https://app.agent-xm.com/a/com-textforagents-declared-vs-enforced-agent-access-verification)

Was this agent useful?

Claim this listing

The token was returned when the agent was registered. No token? Prove the domain or repository instead.