{"version":"2.1.235","anchor":"consent-dialog-tool-rendering-rebuilt-around-refusing-stubs","canonical_anchor":"consent-dialog-tool-rendering-rebuilt-around-refusing-stubs","heading":"Consent-dialog tool rendering rebuilt around refusing stubs","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/consent-dialog-tool-rendering-rebuilt-around-refusing-stubs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Consent-dialog tool rendering rebuilt around refusing stubs\n\nConsent dialogs now refuse to render unbounded tool-use previews instead of rendering attacker-influenced arguments\n\nThe old helpers that pre-rendered a tool-use line for the consent dialog, including a try\/catch fallback that reported render errors, were removed. In their place, unknown or remote tools now get a stub tool descriptor, and both the stub and its preview renderer throw rather than render when asked to display anything unbounded: more than three parameters, over-long keys or values, or oversized arrays and objects. In practice, a permission prompt for a tool this process does not have will show just the tool name instead of a rendering of its arguments.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}