Home / Token cost / AWS Support MCP Server

The AWS Support MCP Server MCP server costs 2,888 tokens before the first call.

Connect AWS Support MCP Server and its 11 tool definitions are loaded into the model's context on every request — 1.4% of a 200k window spent before your agent does anything.

QUICK ANSWER The AWS Support MCP Server MCP server's tool definitions consume 2,888 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 11 tools · 2,888 tokens · 1.4% 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.4%
1M WINDOW 0.3%

Corpus context: AWS Support MCP Server ranks #1323 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 2,888 tokens go.

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

ToolCategoryTokens% of server
create_support_case Write 560 19.4%
describe_support_cases Read 408 14.1%
describe_services Read 355 12.3%
describe_severity_levels Read 252 8.7%
add_attachments_to_set Write 243 8.4%
add_communication_to_case Write 239 8.3%
describe_communications Read 210 7.3%
describe_supported_languages Read 206 7.1%
describe_create_case_options Read 199 6.9%
resolve_support_case Write 112 3.9%
describe_attachment Read 104 3.6%

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

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

Grant scopeDefinition costReduction
All 11 tools (no gateway) 2,888 tokens
3 granted tools ~788 tokens −73%
5 granted tools ~1,313 tokens −55%
10 granted tools ~2,625 tokens −9%

AWS Support MCP Server token-cost questions.

How many tokens does the AWS Support MCP Server MCP server use?+

Its 11 tool definitions total 2,888 tokens — 1.4% 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 AWS Support MCP Server 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 AWS Support MCP Server's token usage?+

Expose fewer tools. A PolicyLayer grant scopes AWS Support MCP Server 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 788 tokens, a 73% 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 11 catalogued AWS Support MCP Server tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes AWS Support MCP Server 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.