Home / Token cost / Governance Platform

The Governance Platform MCP server costs 11,066 tokens before the first call.

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

QUICK ANSWER The Governance Platform MCP server's tool definitions consume 11,066 tokens — 5.8× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 31 tools · 11,066 tokens · 5.5% of 200k · 1.1% 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 5.5%
1M WINDOW 1.1%

Corpus context: Governance Platform ranks #153 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 11,066 tokens go.

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

ToolCategoryTokens% of server
create_blueprint Write 920 8.3%
update_blueprint Write 853 7.7%
decompose_failure Read 550 5.0%
repair_path Read 505 4.6%
create_chain Write 504 4.6%
verify_replay Read 475 4.3%
check_realization Read 461 4.2%
geometric_confidence Read 427 3.9%
get_execution_trace Read 409 3.7%
delete_blueprint Destructive 408 3.7%
handoff_audit Execute 351 3.2%
rotate_api_key Read 329 3.0%
list_blueprints Read 323 2.9%
validate_repair Read 321 2.9%
reject_rule Write 321 2.9%
delete_api_key Destructive 313 2.8%
forecast Read 302 2.7%
structural_types Execute 295 2.7%
list_api_keys Read 277 2.5%
repair Read 276 2.5%
account_status Read 273 2.5%
validate Read 267 2.4%
counterfactual Write 249 2.3%
submit_chain_stage Write 232 2.1%
authorize_execution Write 227 2.1%
load_rule_pack Read 222 2.0%
discover_patterns Read 217 2.0%
check_feasibility Read 215 1.9%
check_drift Read 214 1.9%
analyze_anomaly Read 173 1.6%
approve_rule Write 157 1.4%

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

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

Grant scopeDefinition costReduction
All 31 tools (no gateway) 11,066 tokens
3 granted tools ~1,071 tokens −90%
5 granted tools ~1,785 tokens −84%
10 granted tools ~3,570 tokens −68%

Governance Platform token-cost questions.

How many tokens does the Governance Platform MCP server use?+

Its 31 tool definitions total 11,066 tokens — 5.5% 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 Governance Platform 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 Governance Platform's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Governance Platform 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 1,071 tokens, a 90% 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 31 catalogued Governance Platform tools. Counts refresh with every site build.

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

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