{"version":"2.1.224","anchor":"mcp-telemetry-is-rate-limited-and-tool-names-bucketed","canonical_anchor":"mcp-telemetry-is-rate-limited-and-tool-names-bucketed","heading":"MCP telemetry is rate limited and tool names bucketed","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/mcp-telemetry-is-rate-limited-and-tool-names-bucketed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### MCP telemetry is rate limited and tool names bucketed\n\nMCP telemetry now drops events past a rate limit and reports how many were dropped.\n\n**What**\n\nForwarded events for MCP-style tools now pass through a sliding window per event and server; over the limit, events are dropped and counted, and the next event that gets through reports how many were dropped since the last one.\n\n**Details**\n\n- The window map is size-bounded and evicts its oldest key.\n- Any tool name beginning `skill__` is reported as \"skill\", and feature names starting `tool_skill_` collapse to \"tool_skill\", except `tool_skill_tool`.\n- A denylist of fields is stripped from every payload before it is sent.\n\n**Evidence**\n\n`droppedSinceLastForward`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}