{"version":"2.1.274","anchor":"mcp-server-field-added-to-tool-permission-event-schemas","canonical_anchor":"mcp-server-field-added-to-tool-permission-event-schemas","heading":"mcp_server field added to tool permission event schemas","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/mcp-server-field-added-to-tool-permission-event-schemas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### mcp_server field added to tool permission event schemas\n\nTool permission events now record which MCP server a tool belongs to\n\n**What**\n\nThe event schemas used for tool-use permission requests, denials, and asks (which record things like `tool_name`, `tool_input`, `tool_use_id`, and `permission_suggestions`) now include an optional `mcp_server` field. A new helper function fills this field in by looking up the tool in the MCP (Model Context Protocol) tool registry when a permission decision is made.\n\n**Why**\n\nThis lets permission-related records show which MCP server a tool came from, which is useful for tracking or auditing permission decisions involving tools provided by MCP servers rather than built-in tools.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}