Entity level check if MCP Tool is enabled

[souvikghosh04]

Why make this change?

• Closes on Wire up Entity level MCP config to check if Tool Enabled #3017

The entity-level MCP configuration (Entity.Mcp.DmlToolEnabled or Entity.Mcp.CustomToolEnabled) can override runtime-level settings. DmlToolEnabled defaults to true when unspecified, while CustomToolEnabled defaults to false.
However, this entity-level configuration was not being checked by the MCP tools when they execute. The tools only checked the runtime-level configuration (e.g. RuntimeConfig.McpDmlTools.ReadRecords, etc.).
This change addresses this gap for both built-in/DML tools and custom tools by adding entity-level validation before tool execution.

What is this change?

• Added entity-level configuration checks to all 6 MCP tools (5 DML tools + 1 custom tool) that validate entity-specific flags before executing operations
• DML tools (read_records, create_record, update_record, delete_record, execute_entity) now check entity.Mcp.DmlToolEnabled and return a ToolDisabled error when disabled at the entity level.
• DynamicCustomTool checks entity.Mcp.CustomToolEnabled and return a ToolDisabled error
• Tests covering various scenarios

How was this tested?

• Integration Tests
• Unit Tests

Sample Request(s)

Not applicable since it's a config level change and have been tested based on config settings.

[souvikghosh04]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[Copilot]

Pull request overview

This PR wires entity-level MCP configuration into the MCP tools so that both global runtime and per-entity flags are honored when deciding if a tool is enabled. It also introduces tests to validate behavior for enabled/disabled states, missing MCP config, and custom tools under hot-reload scenarios.

Changes:

• Added DmlToolEnabled checks to all DML MCP tools (read_records, create_record, update_record, delete_record, execute_entity) so they return a ToolDisabled error when disabled at the entity level.
• Added a CustomToolEnabled runtime check in DynamicCustomTool to ensure stored-proc tools are disabled when entity-level config turns them off, even after hot reload.
• Extended MCP error helper to support custom tool-disabled messages and added a dedicated test suite validating entity-level MCP behavior across DML and custom tools.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
src/Service.Tests/Mcp/EntityLevelDmlToolConfigurationTests.cs	New MSTest suite validating entity-level Mcp.DmlToolEnabled and Mcp.CustomToolEnabled handling across DML tools and dynamic custom tools, including disabled entities, enabled/default cases, and missing MCP config.
src/Azure.DataApiBuilder.Mcp/Utils/McpErrorHelpers.cs	Extends ToolDisabled helper with an optional custom message parameter to support more specific error messages while preserving existing call sites.
src/Azure.DataApiBuilder.Mcp/Core/DynamicCustomTool.cs	Adds a runtime check against entityConfig.Mcp.CustomToolEnabled before metadata/authorization, returning a ToolDisabled error when the custom tool is disabled in the current config.
src/Azure.DataApiBuilder.Mcp/BuiltInTools/UpdateRecordTool.cs	After parsing entity/keys/fields, adds an entity-level DmlToolEnabled check that returns ToolDisabled when the entity’s DML tools are disabled.
src/Azure.DataApiBuilder.Mcp/BuiltInTools/ReadRecordsTool.cs	After parsing the entity argument, adds an entity-level DmlToolEnabled check to gate the read_records tool per entity.
src/Azure.DataApiBuilder.Mcp/BuiltInTools/ExecuteEntityTool.cs	Adds an early entity-level DmlToolEnabled check and hardens entity lookup against config.Entities being null before resolving metadata and executing.
src/Azure.DataApiBuilder.Mcp/BuiltInTools/DeleteRecordTool.cs	Adds an entity-level DmlToolEnabled check after parsing entity/keys to prevent deletes when the entity’s DML tools are disabled.
src/Azure.DataApiBuilder.Mcp/BuiltInTools/CreateRecordTool.cs	Adds an entity-level DmlToolEnabled check after parsing entity/data so create operations respect per-entity MCP configuration.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[anushakolan]

The tests code can be refactored to reduce duplicate logic, apart from that rest LGTM. Will re-review once the test code is refactored.

[Aniruddh25]

Waiting on answering if entity level check truly overrides runtime section settings even in case when runtime section is disabled for a particular tool, but the entity level setting is enabled for dml tools.