Home / Token cost / Agentguard

The Agentguard MCP server costs 3,232 tokens before the first call.

Connect Agentguard and its 24 tool definitions are loaded into the model's context on every request — 1.6% of a 200k window spent before your agent does anything.

QUICK ANSWER The Agentguard MCP server's tool definitions consume 3,232 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 24 tools · 3,232 tokens · 1.6% of 200k · 0.3% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 1.6%
1M WINDOW 0.3%

Corpus context: Agentguard ranks #1263 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 3,232 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 135 tokens per tool.

ToolCategoryTokens% of server
audit_log_write Write 210 6.5%
audit_log_query Read 189 5.8%
payment_policy_check Read 176 5.4%
policy_register Write 151 4.7%
payload_safety_check Read 150 4.6%
spend_limit_check Read 148 4.6%
output_safety_scan Read 147 4.5%
replay_guard_check Read 145 4.5%
decision_explain Read 139 4.3%
policy_preflight Read 138 4.3%
session_validate Read 138 4.3%
emergency_kill Read 133 4.1%
approval_resolve Write 133 4.1%
secret_exposure_check Read 132 4.1%
tool_risk_score Destructive 129 4.0%
approval_list Read 127 3.9%
cross_tool_anomaly_check Read 127 3.9%
approval_required Write 124 3.8%
tool_manifest_verify Read 118 3.7%
threat_intel_check Read 113 3.5%
scope_check Read 108 3.3%
tenant_policy_check Read 103 3.2%
rate_limit_check Read 91 2.8%
guard_metrics Read 63 1.9%

Most agents use a handful of these tools. They pay for all 24.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (135 tokens each).

Grant scopeDefinition costReduction
All 24 tools (no gateway) 3,232 tokens
3 granted tools ~404 tokens −88%
5 granted tools ~673 tokens −79%
10 granted tools ~1,347 tokens −58%

Agentguard token-cost questions.

How many tokens does the Agentguard MCP server use?+

Its 24 tool definitions total 3,232 tokens — 1.6% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does Agentguard consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce Agentguard's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Agentguard to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 404 tokens, a 88% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 24 catalogued Agentguard tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes Agentguard to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.