AI and API exposure

A logic block or logic flow does not have to stay inside Logic Fabric. Two switches on its form let other consumers run it directly:

• Expose as MCP Tool makes it a tool that AI agents can run through Logic Conductor.
• Expose as Dataverse Action makes it a Dataverse custom action that Power Automate, plug-ins, client scripts and integrations can call.

The two switches are independent. Turn on either, both or neither.

Dynamics 365 CE on-premisesExpose as ActionApplies to the other edition

On Dynamics 365 CE on-premises the second switch is labelled Expose as Action. It works the same way.

Compare the options

	Expose as MCP Tool	Expose as Dataverse Action
Who calls it	AI agents (for example Claude or GitHub Copilot) connected to Logic Conductor	Anything that can call a Dataverse action
Can you turn it off later?	Yes, at any time	No. Once switched on and saved, it stays on
List inputs and outputs	Supported; lists come back as typed lists	Not allowed
Row outputs	Returned as the row’s data	—
Precondition	Checked on every call, for the signed-in user	Checked on every call, for the calling user

Expose as MCP Tool

Note

AI tools are available in Logic Fabric for Dataverse only. On-premises, use Expose as Action to make logic callable instead.

Turn on Expose as MCP Tool to let AI agents run the block or flow as a tool. Logic Conductor, the Logic Fabric MCP server for running logic, lists exactly the blocks and flows (and business processes) that have this switch on. An agent sees the tool with its inputs and outputs, runs it as the signed-in user, and gets the outputs back.

1. Open the logic block or logic flow.
2. Turn on Expose as MCP Tool.
3. Save.
4. Make sure the project is one that Logic Conductor is set up to expose. See Set up Logic Conductor.

To help an agent pick the right tool and fill it in correctly:

• Give the block or flow a clear name, such as Calculate Quote Discount.
• Write a Description on the Docs tab that says what it does and when to use it.
• Name inputs and outputs in plain words (QuoteAmount, not amt1).
• Use a precondition for anything an agent must not run for everyone.

You can turn the switch off at any time. Logic Conductor picks up switches turned on or off, and changes to a tool’s name, description, inputs or outputs, the next time it restarts; see Set up Logic Conductor.

Expose as Dataverse Action

Turn on Expose as Dataverse Action to make the block or flow callable as a Dataverse custom action, with its inputs as action parameters and its outputs as the action’s response.

This is a one-way switch

Once Expose as Dataverse Action is switched on and saved, it stays on: the field locks. Other systems may now depend on the action, so plan it as a public contract before you save.

Lists are not allowed

Dataverse actions do not support list arguments. On a block or flow exposed as a Dataverse action:

• The List of values switch is hidden on inputs and outputs.
• If a block or flow already has list inputs or outputs, turning on Expose as Dataverse Action is refused with a message such as: “Logic block ‘Eligible Products’ cannot be exposed as an action because these arguments are lists: Products. Actions do not support list arguments.”

If you need lists and a Dataverse action, put the list logic in one block or flow and expose a second one that calls it and returns single values.

Example

The Calculate Quote Discount decision table returns DiscountPercent and DiscountReason.

• The sales team’s AI assistant should answer “What discount can I give Contoso on this quote?” Turn on Expose as MCP Tool.
• A Power Automate flow that prices quotes from the website also needs it. Its inputs and outputs are single values, so turn on Expose as Dataverse Action too, knowing it stays on.

Related

• Logic Conductor
• Preconditions
• Inputs and outputs
• Logic API