Home / Token cost / Nullcone Threat Intelligence

The Nullcone Threat Intelligence MCP server costs 6,097 tokens before the first call.

Connect Nullcone Threat Intelligence and its 30 tool definitions are loaded into the model's context on every request — 3.0% of a 200k window spent before your agent does anything.

QUICK ANSWER The Nullcone Threat Intelligence MCP server's tool definitions consume 6,097 tokens — 3.2× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 30 tools · 6,097 tokens · 3.0% of 200k · 0.6% 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 3.0%
1M WINDOW 0.6%

Corpus context: Nullcone Threat Intelligence ranks #957 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 6,097 tokens go.

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

ToolCategoryTokens% of server
subscribe_threats Read 501 8.2%
fingerprint_tool_metadata Read 462 7.6%
scan_skill_content Read 448 7.3%
submit_ioc Write 440 7.2%
check_freshness Read 366 6.0%
check_prompt Read 332 5.4%
validate_skill Read 281 4.6%
revoke_ioc Destructive 268 4.4%
poll_since Read 229 3.8%
search_by_type Read 220 3.6%
get_new_threats Read 217 3.6%
drain_subscription Destructive 202 3.3%
report_detection Read 186 3.1%
submit_batch Write 186 3.1%
list_revocations Read 161 2.6%
warm_prompt_cache Write 146 2.4%
family_threats Read 145 2.4%
is_ioc_revoked Read 144 2.4%
unsubscribe Destructive 142 2.3%
vote_false_positive Write 140 2.3%
check_prompt_batch Read 130 2.1%
recent_threats Read 115 1.9%
lookup_ioc Read 110 1.8%
freshness_limits Read 82 1.3%
list_families Read 82 1.3%
list_subscriptions Read 82 1.3%
prompt_cache_stats Read 77 1.3%
registry_flagged_tools Write 75 1.2%
registry_monitor_stats Read 66 1.1%
get_stats Read 62 1.0%

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

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

Grant scopeDefinition costReduction
All 30 tools (no gateway) 6,097 tokens
3 granted tools ~610 tokens −90%
5 granted tools ~1,016 tokens −83%
10 granted tools ~2,032 tokens −67%

Nullcone Threat Intelligence token-cost questions.

How many tokens does the Nullcone Threat Intelligence MCP server use?+

Its 30 tool definitions total 6,097 tokens — 3.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 Nullcone Threat Intelligence 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 Nullcone Threat Intelligence's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Nullcone Threat Intelligence 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 610 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 30 catalogued Nullcone Threat Intelligence tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Nullcone Threat Intelligence 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.