Home / Token cost / AiEGIS

The AiEGIS MCP server costs 1,858 tokens before the first call.

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

QUICK ANSWER The AiEGIS MCP server's tool definitions consume 1,858 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 18 tools · 1,858 tokens · 0.9% 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 0.9%
1M WINDOW 0.2%

Corpus context: AiEGIS ranks #1627 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,858 tokens go.

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

ToolCategoryTokens% of server
grid_create_mandate Write 308 16.6%
grid_pay Financial 138 7.4%
grid_route_mandate_for_approval Read 135 7.3%
grid_register Write 119 6.4%
grid_rate Execute 118 6.4%
grid_inquire Execute 115 6.2%
grid_search Read 115 6.2%
grid_send_message Write 110 5.9%
grid_counter Write 100 5.4%
grid_propose Read 99 5.3%
grid_get_mandate_status Read 89 4.8%
grid_my_deals Read 74 4.0%
grid_accept_deal Read 72 3.9%
grid_get_agent Read 66 3.6%
grid_pending_approvals Read 56 3.0%
grid_discover Read 54 2.9%
grid_deal_status Read 47 2.5%
grid_health Read 43 2.3%

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

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

Grant scopeDefinition costReduction
All 18 tools (no gateway) 1,858 tokens
3 granted tools ~310 tokens −83%
5 granted tools ~516 tokens −72%
10 granted tools ~1,032 tokens −44%

AiEGIS token-cost questions.

How many tokens does the AiEGIS MCP server use?+

Its 18 tool definitions total 1,858 tokens — 0.9% 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 AiEGIS 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 AiEGIS's token usage?+

Expose fewer tools. A PolicyLayer grant scopes AiEGIS 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 310 tokens, a 83% 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 18 catalogued AiEGIS tools. Counts refresh with every site build.

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

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