{"version":"2.1.280","anchor":"new-telemetry-mcp-inline-tools-remote-control-entry-plugi","canonical_anchor":"new-telemetry-mcp-inline-tools-remote-control-entry-plugi","heading":"New telemetry: mcp_inline_tools, remote_control_entry, plugin_version_sha","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-telemetry-mcp-inline-tools-remote-control-entry-plugi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New telemetry: mcp_inline_tools, remote_control_entry, plugin_version_sha\n\nThree new telemetry identifiers added: mcp_inline_tools, remote_control_entry, and plugin_version_sha\n\n**Unclear.** The finding does not say what specifically each event or field records or when it fires.\n\n**What**\n\nThree new names were added to the known-telemetry allowlist:\n\n- `mcp_inline_tools`, an MCP-related event\n\n- `remote_control_entry`, a remote-control event\n\n- `plugin_version_sha`, a redaction field\n\n**Why**\n\nAdding these to the allowlist means telemetry involving MCP inline tools, remote control entries, and plugin version hashes can now be recorded and handled properly (including redaction for the sha field), rather than being blocked or unrecognized.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}