MCP telemetry now drops events past a rate limit and reports how many were dropped.
What's wrong with this entry?
Forwarded 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.
- The window map is size-bounded and evicts its oldest key.
- Any tool name beginning
skill__is reported as "skill", and feature names startingtool_skill_collapse to "tool_skill", excepttool_skill_tool. - A denylist of fields is stripped from every payload before it is sent.
droppedSinceLastForward
Strings lifted out of the shipped bundle, so the claim above can be checked against them.