Controlled tool use

Expose support actions as approved tools.

Approved tools let Aura and operators query context, prepare updates, trigger workflows, and package actions while permissions and approvals decide what can run.

Intent detectedPermission checkedAction preparedHuman approves if needed

Approved tools

actions Aura can use

approved support tools

MCP tool execution panel

permission scoped

Tool registry

customer.lookup

read customer profile

approved

support scope

ticket.update

tag, assign, status

agent scope

refund.prepare

create preview only

warning

manager approval

workflow.trigger

SLA escalation

queue rules

Execution preview

tool: refund.prepare
ticket: REP-1842
order: 10482
amount: 14.00
source: Returns policy v2.4
state: awaiting_manager_approval

permission01

Validate scope

Agent can prepare but cannot execute the refund.

source02

Attach evidence

Policy source and order record are linked to the request.

audit03

Write audit

Tool request is logged before approval.

Tools overview

MCP Tools

Approved tools let Aura and operators query context, prepare updates, trigger workflows, and package actions while permissions and approvals decide what can run.

How it works

actions Aura can use

Intent detected

Aura identifies that a tool could help resolve the case.

Permission checked

Role, workflow, data class, and approval requirements are evaluated.

Action prepared

The tool returns context or prepares an operation.

Human approves if needed

Sensitive actions stay behind review.

Operational capability

Support resolution often requires action, not just an answer.

Approved tools give Aura a controlled way to look up context, prepare changes, and trigger workflows.

Problem 01

Customer lookup

Retrieve account, order, or ticket context when allowed.

Problem 02

Ticket update

Prepare status, tag, owner, or priority changes.

Problem 03

Refund preparation

Package a refund request for human approval.

Tool-call lifecycle

Every tool use has a boundary and trace.

Detect

Intent detected

Aura identifies that a tool could help resolve the case.

Guard

Permission checked

Role, workflow, data class, and approval requirements are evaluated.

Prepare

Action prepared

The tool returns context or prepares an operation.

Approve

Human approves if needed

Sensitive actions stay behind review.

Audit

Audit logged

Tool, source, input, output, and decision stay visible.

Examples

Common MCP support tools.

Tool

Used for

Boundary

Tool

customer.lookup

Used for

Find account and history

Boundary

Read-only scope

Tool

ticket.update

Used for

Set status, owner, tags

Boundary

Workflow permission

Tool

refund.prepare

Used for

Package refund request

Boundary

Approval required

Tool

workflow.trigger

Used for

Route escalation or timing rule

Boundary

Logged execution

See what to read next.

Tools

SDKSoon

The SDK/API surface is for teams that need ticket creation, workflow triggers, analytics reads, and internal support operations inside product or admin tools.

Tools

Skills

Skills shape how Aura handles refunds, bugs, angry customers, missing information, fallback, and handoff while staying tied to sources and approvals.

Tools

Integrations Hub

The Integrations Hub shows what Replofy can read, where conversations enter, which tools Aura can use, and how connection health is monitored.

Design approved tools

Make AI useful beyond writing text.

Expose approved support actions as auditable tools with permission boundaries.

Book a demo