{"version":"2.1.224","anchor":"telemetry-forwarding-now-strips-identifying-fields-and-caps-","canonical_anchor":"telemetry-forwarding-now-strips-identifying-fields-and-caps-","heading":"Telemetry forwarding now strips identifying fields and caps MCP event volume","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/telemetry-forwarding-now-strips-identifying-fields-and-caps-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Telemetry forwarding now strips identifying fields and caps MCP event volume\n\nInternal metrics forwarding strips identifying fields, buckets tool names and caps per-server MCP volume.\n\n**What**\n\nThe internal metrics forwarder, reached only on first-party accounts, now removes a list of potentially identifying fields before sending, collapses tool and feature names into generic buckets, and limits how often per-server MCP events can be sent.\n\n**Details**\n\n- Deleted fields include the MCP server base URL and name, the MCP tool name, a hashed error message, and two hashed skill names.\n- Any tool name collapses to `mcp` when the event is flagged as MCP, where previously only names beginning with `mcp__` were collapsed. Names beginning with `skill__` become `skill`, and feature names beginning with `tool_skill_` become `tool_skill`, except `tool_skill_tool`.\n- Five MCP events are capped at 10 forwards per 60 second window per server, tracked across at most 200 server keys, and the count suppressed since the last send rides along as `droppedSinceLastForward`.\n\n**Evidence**\n\n`stripPiiFieldsForDatadog`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}