Can Lyro run a function against preprod without touching production?

Yes. Each environment has its own actions rather than an environment flag: preprod has POST, PUT, and DELETE variants, dev has a PATCH variant, and production has its own GET action. The environment is decided by which action is called, so a test run cannot silently hit live.

Does Lyro write raw SQL against the Cloud DB?

No. The Visual SQL SELECT, Update, and Delete actions execute Visual SQL functions that already exist in AppDrag, so the table and the query shape come from that function and Lyro only supplies its parameters. A query nobody built is a query Lyro cannot run.

Can Lyro create a database table or edit website content in AppDrag?

No. Every action in this toolkit executes something that already exists - a Cloud Backend API function or a Visual SQL function. Schema changes, page building, and content editing stay in the AppDrag editor.

What limits the damage a delete can do?

Visual SQL Delete only runs the delete function you defined, so its conditions are fixed in AppDrag rather than composed in the conversation. There is also a preprod DELETE action, which is the sensible place to validate a delete operation before the same call runs on live data.

Appdrag MCP integration

Calls Cloud Backend functions on prod, preprod, or dev with the verb they expect, and runs Visual SQL reads, updates, and deletes on the Cloud DB.

Connect Appdrag See all integrations

11actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Execute cloud backend function via post
Lyro calls your custom backend function to process data or trigger workflows in production. Results return instantly without requiring manual server access.
Visual SQL select
Lyro queries your database and returns matching records based on your conditions. Data lookups execute without requiring SQL expertise or database access.
Visual SQL update
Lyro modifies database records based on conditions you specify in your request. Data stays synchronized as business operations and customer accounts change.

See all 11 actions

How businesses use Appdrag + Lyro

Each card is one request a support team gets, and the Appdrag actions Lyro runs to close it.

Call a backend function on the live environment
Lyro invokes a production Cloud Backend function with GET, or sends parameters through POST or PUT on the default environment, so an existing routine runs without a deploy or a console session.
Execute PROD API Function (GET)Execute Cloud Backend Function via POSTExecute Cloud Backend Function via PUT
Validate the same call in preprod or dev first
Lyro runs the preprod copy of a function before anyone points it at live data, and calls the dev version with PATCH right after a function has been updated there.
Execute Preprod Function (DELETE)Execute Function POST (Preprod Env)Execute Dev Function (PATCH)
Read and correct rows in the Cloud DB
Lyro runs a Visual SELECT function to read rows from a table and a Visual UPDATE function to change them, using the queries your team already built rather than free-form SQL.
Visual SQL SELECTVisual SQL Update
Remove records through a defined delete path
Lyro deletes rows through a Visual SQL Delete function or calls a Cloud Backend function with DELETE, so removals follow a route someone designed instead of an ad hoc statement.
Visual SQL DeleteExecute Cloud Backend Function DELETE

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Appdrag actions it has and picks the ones a request needs.

01
Connect Appdrag
Authorize the Appdrag account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Appdrag actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Appdrag · Lyro

Everything else about Appdrag

Setup, permissions, and the limits of what Lyro can do inside Appdrag.

Yes. Each environment has its own actions rather than an environment flag: preprod has POST, PUT, and DELETE variants, dev has a PATCH variant, and production has its own GET action. The environment is decided by which action is called, so a test run cannot silently hit live.

Every action available in Appdrag

All 11 actions your agent can call on Appdrag, straight from the live MCP connection.

Execute cloud backend function via delete
Execute a Cloud Backend API function via DELETE on the default environment.
Execute preprod function (delete)
Execute the pre-production version of a Cloud Backend API function via DELETE.
Execute prod API function (get)
Execute a production Cloud Backend API function via GET.
Execute dev function (patch)
Execute the development version of a Cloud Backend API function via PATCH.
Execute cloud backend function via post
Execute a Cloud Backend API function via POST on the default environment.
Execute function post (preprod env)
Execute a Cloud Backend API function via POST on the preprod environment.
Execute cloud backend function via put (default)
Execute a Cloud Backend API function via PUT on the default environment.
Execute cloud backend function via put (preprod)
Execute a Cloud Backend API function via PUT on the preprod environment.
Visual SQL delete
Delete rows via a Visual SQL Delete function.
Visual SQL select
Execute a Visual SELECT Cloud Backend function.
Visual SQL update
Execute a Visual SQL UPDATE via an AppDrag Visual UPDATE function.