agentguard — policy proxy for agent tool calls
REMOTE · AGENTWARES-AGENTGUARD.VERCEL.APP · SCANNED SEP 25
Free spend report from an agent log, no key. Hosted proxies: caps, audit export, buy calls.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1129 tokens (~161/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the agentguard — policy proxy for agent tool calls MCP server?
agentguard — policy proxy for agent tool calls is a hosted endpoint at https://agentwares-agentguard.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentwares-agentguard.vercel.app
claude mcp add --transport http agentwares-agentguard-cloud 'https://agentwares-agentguard.vercel.app/api/mcp'
{
"mcpServers": {
"agentwares-agentguard-cloud": {
"url": "https://agentwares-agentguard.vercel.app/api/mcp"
}
}
} {
"servers": {
"agentwares-agentguard-cloud": {
"type": "http",
"url": "https://agentwares-agentguard.vercel.app/api/mcp"
}
}
} [mcp_servers.agentwares-agentguard-cloud] url = "https://agentwares-agentguard.vercel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agentwares-agentguard-cloud": {
"type": "remote",
"url": "https://agentwares-agentguard.vercel.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add agentwares-agentguard-cloud --url 'https://agentwares-agentguard.vercel.app/api/mcp' --transport streamable-http
mcp_servers:
agentwares-agentguard-cloud:
url: "https://agentwares-agentguard.vercel.app/api/mcp" {
"McpServers": {
"agentwares-agentguard-cloud": {
"Transport": "http",
"Url": "https://agentwares-agentguard.vercel.app/api/mcp"
}
}
} assistant mcp add agentwares-agentguard-cloud -t streamable-http -u 'https://agentwares-agentguard.vercel.app/api/mcp'
{
"mcpServers": {
"agentwares-agentguard-cloud": {
"type": "http",
"url": "https://agentwares-agentguard.vercel.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 128 → 161 ▼ functional
- Server version: 0.1.1 → 0.2.0 functional
- New tool “agentguard_spend_report” functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://agentwares-agentguard.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentwares-agentguard.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentwares-agentguard.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://agentwares-agentguard.vercel.app/api/mcp | HTTPS enforced | 308 | https://agentwares-agentguard.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agentguard_create_proxy ~150
Create a hosted agentguard proxy in front of an MCP server. Returns the proxy id, the per-customer MCP URL and the proxy key (shown once). Point your agent's MCP client at the URL with `Authorization: Bearer <key>`. Requires an account key.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | dry-run records what the policy would have blocked and lets every call through; enforce actually blocks. Start in dry-run. |
| slug | string | yes | short name, a-z 0-9 - |
| upstreamName | string | – | name used to namespace tools when you add more upstreams later |
| upstreamUrl | string | yes | Streamable HTTP URL of the MCP server to protect |
No output schema declared.
No examples provided.
agentguard_export_audit ~101
Export a run's hash-chained audit entries (prev_hash, hash, redacted args) with the Merkle root, for disputes and questionnaires. Verify offline with sha256(prev_hash + canonical(entry)). Requires an account key.
| Name | Type | Req | Description |
|---|---|---|---|
| proxyId | string | yes | the proxy id returned by agentguard_create_proxy |
| runId | string | yes | the X-Run-Id your agent sent with the calls; one run is one agent session |
No output schema declared.
No examples provided.
agentguard_get_pricing ~96
Machine-readable pricing for agentguard hosted: bands (Starter/Pro/Team) with included tool calls per month, the 80% soft alert and 150% hard stop, features, the free trial allowance, and `per_call` — buying tool calls outright at POST /api/v1/calls from a prepaid balance, which is the one purchase here an unattended agent can complete. Same data as /pricing.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agentguard_get_run ~105
The incident-shaped report for one run: counts (calls, reads, writes, faked, blocked, spend), the call timeline with decisions, dry-run mutations (what would have changed), ledger entries and the audit-chain verification. Requires an account key.
| Name | Type | Req | Description |
|---|---|---|---|
| proxyId | string | yes | the proxy id returned by agentguard_create_proxy |
| runId | string | yes | the X-Run-Id your agent sent with the calls; one run is one agent session |
No output schema declared.
No examples provided.
agentguard_recommend_allowlist ~81
Least-privilege recommendation from the proxy's recorded calls: the minimal tool allowlist, argument keys used per tool, and the upstream tools never used (remove them first). No LLM call here; apply it in the dashboard. Requires an account key.
| Name | Type | Req | Description |
|---|---|---|---|
| proxyId | string | yes | the proxy id returned by agentguard_create_proxy |
No output schema declared.
No examples provided.
agentguard_set_policy ~96
Replace a proxy's policy (YAML: mode, upstreams, classify, caps, loop, dry_run, approvals, alerts, chaos, drift). Validated before saving; takes effect within 30 seconds. Requires an account key.
| Name | Type | Req | Description |
|---|---|---|---|
| policyYaml | string | yes | the complete policy document; it replaces the current one rather than merging |
| proxyId | string | yes | the proxy id returned by agentguard_create_proxy |
No output schema declared.
No examples provided.
agentguard_spend_report ~317
Read an agent log and report what it spent: totals, calls by tool and by class, estimated dollars by rail, loops, the largest single run, and — for every overspend — the agentguard band whose cap would have stopped it, the exact cap, and the call that would have tripped it. Needs no account and no key. The log is read in the request and discarded; nothing is stored. Accepts an agentwares audit export (`agentwares.audit/v1`), a Claude Code session `.jsonl`, or a CSV/JSONL of tool calls with any of `tool`, `ts`, `class`, `amount_usd`, `rail`, `run_id`, `model`, `input_tokens`, `output_tokens`. Caps come from the proxy's own default policy, so a band named here refuses exactly what it says it refuses. Buying that band is a checkout a person completes; the calls-only purchase an unattended agent can complete is in `agentguard_get_pricing` instead.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | `concise` (default) returns the totals, the top ten tools, the rails, the loops and every overspend. `full` adds the complete per-tool breakdown and the window. Ask for `full` only when you are going… |
| log | string | yes | The log itself, verbatim — JSON, JSONL or CSV. Not a path and not a URL: this server does not fetch anything. |
No output schema declared.
No examples provided.
What is the agentguard — policy proxy for agent tool calls MCP server?
agentguard — policy proxy for agent tool calls is an MCP server listed in the public MCP registry as io.github.agentwares/agentguard-cloud. Free spend report from an agent log, no key. Hosted proxies: caps, audit export, buy calls. This page covers its hosted endpoint (https://agentwares-agentguard.vercel.app/api/mcp).
Is the agentguard — policy proxy for agent tool calls MCP server safe to use?
agentguard — policy proxy for agent tool calls scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the agentguard — policy proxy for agent tool calls MCP server expose?
agentguard — policy proxy for agent tool calls exposes 7 tools: agentguard_get_pricing, agentguard_spend_report, agentguard_create_proxy, agentguard_set_policy, agentguard_get_run, and 2 more. Their descriptions and schemas cost roughly 946 tokens of context every time the server is loaded.
Does the agentguard — policy proxy for agent tool calls MCP server require authentication?
No. We connected to agentguard — policy proxy for agent tool calls without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the agentguard — policy proxy for agent tool calls MCP server still maintained?
agentguard — policy proxy for agent tool calls is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.