Home / Token cost / Dock

The Dock MCP server costs 17,999 tokens before the first call.

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

QUICK ANSWER The Dock MCP server's tool definitions consume 17,999 tokens — 9.4× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 64 tools · 17,999 tokens · 9.0% of 200k · 1.8% 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 9.0%
1M WINDOW 1.8%

Corpus context: Dock ranks #63 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 17,999 tokens go.

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

ToolCategoryTokens% of server
update_doc Write 1,449 8.1%
update_doc_section Write 622 3.5%
create_row Write 540 3.0%
update_surface Write 540 3.0%
update_row Write 534 3.0%
send_message Write 533 3.0%
create_workspace Write 521 2.9%
add_comment Write 516 2.9%
update_workspace Write 499 2.8%
append_doc_section Read 495 2.8%
list_comments Read 468 2.6%
update_html Write 456 2.5%
get_doc Read 436 2.4%
add_column Write 424 2.4%
upgrade_plan Write 410 2.3%
create_surface Write 365 2.0%
move_rows Write 318 1.8%
create_webhook Write 313 1.7%
evaluate_formula Read 292 1.6%
create_support_ticket Write 290 1.6%
remove_workspace_member Destructive 286 1.6%
list_rows Read 280 1.6%
delete_workspace Destructive 277 1.5%
list_sheet_functions Read 270 1.5%
get_workspace_schema Read 265 1.5%
downgrade_plan Write 260 1.4%
search Read 255 1.4%
validate_html Read 252 1.4%
request_revoke_agent_key Destructive 245 1.4%
list_files Read 241 1.3%
validate_doc_markdown Read 233 1.3%
share_workspace Destructive 230 1.3%
reply_to_comment Write 228 1.3%
validate_formula Read 217 1.2%
react_to_comment Write 209 1.2%
get_file Read 204 1.1%
update_workspace_member Write 194 1.1%
share_file Destructive 191 1.1%
list_surfaces Read 189 1.1%
request_rotate_agent_key Destructive 182 1.0%
get_html Read 182 1.0%
delete_file Destructive 168 0.9%
revoke_file_share Destructive 165 0.9%
rotate_api_key Destructive 161 0.9%
list_recent_files Read 161 0.9%
get_workspace Read 159 0.9%
delete_surface Destructive 155 0.9%
address_book Read 154 0.9%
list_workspace_members Read 148 0.8%
request_limit_increase Read 148 0.8%
update_webhook Write 142 0.8%
rotate_webhook_secret Read 133 0.7%
list_webhooks Read 132 0.7%
revoke_api_key Destructive 131 0.7%
get_row Read 129 0.7%
get_comment_thread Read 120 0.7%
list_workspaces Read 119 0.7%
resolve_comment Write 119 0.7%
get_billing Read 117 0.7%
get_recent_events Read 117 0.7%
delete_row Destructive 108 0.6%
delete_webhook Destructive 107 0.6%
unresolve_comment Write 107 0.6%
list_api_keys Read 88 0.5%

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

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

Grant scopeDefinition costReduction
All 64 tools (no gateway) 17,999 tokens
3 granted tools ~844 tokens −95%
5 granted tools ~1,406 tokens −92%
10 granted tools ~2,812 tokens −84%

Dock token-cost questions.

How many tokens does the Dock MCP server use?+

Its 64 tool definitions total 17,999 tokens — 9.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 Dock 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 Dock's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Dock 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 844 tokens, a 95% 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 64 catalogued Dock tools. Counts refresh with every site build.

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

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