Home / Token cost / AgentBond

The AgentBond MCP server costs 1,941 tokens before the first call.

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

QUICK ANSWER The AgentBond MCP server's tool definitions consume 1,941 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 17 tools · 1,941 tokens · 1.0% of 200k · 0.2% 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.0%
1M WINDOW 0.2%

Corpus context: AgentBond ranks #1595 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 1,941 tokens go.

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

ToolCategoryTokens% of server
agentbond_issue_token Write 365 18.8%
agentbond_create_contract Write 313 16.1%
agentbond_evaluate_action Read 260 13.4%
agentbond_record_intent Read 234 12.1%
agentbond_evaluate_intent_policy Read 133 6.9%
agentbond_transition_contract Read 116 6.0%
agentbond_get_audit_log Read 101 5.2%
agentbond_evaluate_contract Read 56 2.9%
agentbond_revoke_token Destructive 53 2.7%
agentbond_suspend_token Write 50 2.6%
agentbond_reactivate_token Read 42 2.2%
agentbond_get_audit_by_action Read 39 2.0%
agentbond_get_audit_by_token Read 39 2.0%
agentbond_get_intent_by_action Read 38 2.0%
agentbond_get_intent Read 35 1.8%
agentbond_get_token Read 34 1.8%
agentbond_get_contract Read 33 1.7%

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

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 (114 tokens each).

Grant scopeDefinition costReduction
All 17 tools (no gateway) 1,941 tokens
3 granted tools ~343 tokens −82%
5 granted tools ~571 tokens −71%
10 granted tools ~1,142 tokens −41%

AgentBond token-cost questions.

How many tokens does the AgentBond MCP server use?+

Its 17 tool definitions total 1,941 tokens — 1.0% 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 AgentBond 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 AgentBond's token usage?+

Expose fewer tools. A PolicyLayer grant scopes AgentBond 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 343 tokens, a 82% 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 17 catalogued AgentBond tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes AgentBond 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.