AI Agent Studio Business Object Tools
Business Object tools in Oracle AI Agent Studio allow AI agents to retrieve, update, create or delete Oracle Fusion Cloud Applications business object records. Builders select which business objects and fields the tool may use or ignore. This record covers the Business Object tool mechanism only, not connector, email, document, deep link, MCP or external REST tools.
Recorded characteristics
- Function
- Oracle documents Business Object tools as one of the tool types that can be assigned to AI agents in AI Agent Studio. Oracle states that Business Object tools allow AI agents to retrieve, update, create or delete business object records within Fusion Applications, and that agents can use the tool to access information or call specific functions in the application. Business Object also appears as a Data node type available in AI Agent Studio workflows.
- Data access
- Oracle states that the data available to the agent through this tool is controlled by selecting the business objects and fields to use or ignore. Access is to Fusion Applications business object records within the selected objects and fields. Oracle states that AI agents adhere to the native security and role-based access controls of Fusion Applications. Current documentation does not establish access beyond Fusion business objects through this tool.
- Actions
- Can take actions
- External actions
- Unknown
- Human confirmation
- Conditional
- Permission basis
- Not established
- Administrative control
- Oracle documents that builders select the business objects and fields the tool can use or ignore. Access to configure AI agents in AI Agent Studio is granted by assigning predefined duty roles to job roles, with documented prerequisites including enabling the Security Console to work with permission groups and running security data import scheduled processes. Oracle documents removing the related custom roles to restrict a user's access to AI Agent Studio. Human approval is configured separately, through a Human-in-the-Loop flag on tool use and through Human Approval nodes associated with published approval processes in workflows.
- Default state
- Not established
- Availability
- Documented as part of AI Agent Studio within Oracle Fusion Cloud Applications. Oracle documents separate access-provisioning pages for Fusion Cloud HCM, SCM, Procurement, Financials, CX and Oracle Permitting and Licensing. Current documentation reviewed does not establish availability across every Fusion product, region, tenant or subscription.
- Licensing
- Not established in the reviewed current Oracle documentation.
- External model or provider
- Not established for this capability. Oracle states that Fusion Cloud Applications support several large language models from providers such as Cohere, Meta and OpenAI, and that agents can use a default model or a selected custom model, but no single model or provider is established for Business Object tool use.
- Limitations and uncertainty
- Oracle states that AI agents adhere to the native security and role-based access controls of Fusion Applications, but the reviewed documentation does not state whose identity governs runtime business object access (the invoking user, an agent identity, or another mechanism), so permission basis is recorded as not established. Human approval is recorded as conditional because Oracle documents a Human-in-the-Loop flag that determines whether explicit user approval is required and Human Approval nodes that can be added to workflows; approval is not documented as mandatory for all Business Object state-changing actions. Whether the tool is enabled or in use by default is not established, because Oracle documents it as a resource that builders create and assign. Current Oracle documentation for release 26C does not include a dedicated Business Object tool configuration page; the mechanism is documented in the Get Started, Components and Nodes pages.
Evidence
- Get Started with AI Agent Studio
Supports: Function · Actions · Data access · Admin controls · Permission basis · General · Primary source
Business Object tools allow AI agents to retrieve, update, create or delete business object records within Fusion Applications.
Documented operations are retrieve, update, create and delete on Fusion business object records.
Builders control what data agents can access by selecting the business objects and fields to use or ignore.
Selection of business objects and fields is the documented configuration control for this tool.
Oracle states agents adhere to native Fusion security and role-based access controls, without specifying the runtime identity.
Business Object tools are created as a resource before agents and workflows are built.
- Components of AI Agent Studio
Supports: Function · General · Primary source
Business object is listed as a distinct tool type assignable to agents.
Connector, email, document, deep link and external REST are documented as separate tool types.
- Nodes in Workflows
Supports: Function · Human confirmation · Primary source
Business Object is available as a Data node type in AI Agent Studio workflows.
Human Approval is a separate, optional workflow control node.
- Single Agent with Multiple Tools and a Human in the Loop
Supports: Human confirmation · Primary source
A Human-in-the-Loop flag determines whether a user must give explicit approval before the agent proceeds.
- Add an Approval Process Channel to a Human Approval Node of Workflows
Supports: Human confirmation · Admin controls · Primary source
Human approval nodes pause a workflow while approval is routed through a published approval process; they are added by configuration.
Approval processes, notification channels, approval levels and approver rules are configured by builders.
- Access Requirements for AI Agent Studio
Supports: Admin controls · Permission basis · Availability · Primary source
Access to configure AI agents is granted through predefined duty roles assigned to job roles, plus documented prerequisites.
Documents builder and administrator configuration access, distinct from runtime access for a deployed agent.
Separate access provisioning is documented per Fusion product family.
- Key Capabilities of AI Agent Studio
Supports: Permission basis · Availability · Primary source
AI Agent Studio automatically applies the security configurations, policies and access controls of Fusion Applications.
Native integration with Fusion Applications APIs and tools.
- Which large language models (LLMs) are currently used or supported for AI agents?
Supports: External model · Limitations · Primary source
Several LLMs from providers such as Cohere, Meta and OpenAI are supported; no single model or provider is established for this capability.
Model selection is configurable, so no universal model or provider can be recorded for this capability.