{"version":"2.1.235","anchor":"mcp-tool-permission-dialogs-render-parameters-as-a-keyvalue","canonical_anchor":"mcp-tool-permission-dialogs-render-parameters-as-a-keyvalue","heading":"MCP tool permission dialogs render parameters as a key\/value table","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/mcp-tool-permission-dialogs-render-parameters-as-a-keyvalue","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### MCP tool permission dialogs render parameters as a key\/value table\n\nMCP tool permission dialogs now render parameters as a formatted key\/value table with links and timestamps\n\nPermission dialogs for MCP tools now build structured entries per parameter, laid out inline or as a bordered block. A `code` parameter with a short sibling `language` value gets syntax highlighting, http(s) links become clickable, and values whose JSON Schema declares `format: date-time`, or Slack-style `ts`\/`thread_ts` epoch strings, get a human-readable timestamp annotation.\n\nRendering is bounded throughout: 80 columns for inline layout, a 200,000 code-unit budget per key or value, 64 levels of nesting, and highlighting is skipped past 50,000 characters.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}