Platform actions for Trace AI

Trace AI can perform read and write operations on your tenant data through MCP tools registered in mcp_resources. Tools use the same tenant and user context as the console UI.

Activation

There is no global “platform actions” feature flag. Each tool is enabled individually via mcp_resources.is_active. Disable a tool by setting is_active = 0 on its row.

Skills + tools workflow

See Platform skills quick reference for the full skill → tool map.

Load the platform-actions skill (load_platform_skill) for orchestration guidance.
For writes, call describe_* tools first to learn accepted fields.
Call list_* / get_* read tools to gather ids and current state.
Use request_human_input (confirm) before destructive or high-risk actions when appropriate.
Call the write or execute tool with a minimal payload.

Read tools (Phase 1)

Tool	Purpose
`list_entities`, `get_entity`	Entity catalog
`list_products`, `get_product`	Products
`list_contracts`, `get_contract`	Contracts
`list_processes`, `get_process`	Process definitions
`list_integrations`, `get_integration`	Integrations (no secrets in list)
`list_webapps`, `get_webapp`	WebApps
`query_datapool`	Datapool rows by schema
`query_monitor_logs`	Process/integration execution logs
`list_notifications`	User notifications
`read_todo_list`	Tenant chat TODO list

Describe tools

Tool	Purpose
`describe_entity`	Entity create/update field contract
`describe_product`	Product create/update contract
`describe_contract`	Contract create/update contract
`describe_process`	Execute requirements, triggers, `executable_by_ai_agents`
`describe_tenant_integration`	Integration operations and payload shapes

Write tools (Phase 2)

Tool	Notes
`create_entity`, `update_entity`, `delete_entity`	Delete archives (`status=archived`)
`create_product`, `update_product`, `delete_product`	Delete sets `status=DELETED`
`create_contract`, `update_contract`, `delete_contract`	Hard delete on contract row
`execute_process`	Requires Executable by AI Agents on the process
`run_process_trigger`	Fire trigger; same opt-in gate as `execute_process`
`test_integration`	Configuration validation (same as UI test)
`execute_tenant_integration`	Requires Executable by AI Agents on the integration
`create_integration`, `update_integration`, `delete_integration`	Integration CRUD
`create_datapool_schema`, `update_datapool_schema`	Datapool schema management
`insert_datapool_rows`, `update_datapool_rows`, `delete_datapool_rows`	Datapool row CRUD
`create_entity_relationship`, `delete_entity_relationship`	Entity linkage graph

Builder tools (Phase 3)

Tool	Notes
`create_process`, `update_process`, `retire_process`	Process definitions; `retire_process` sets inactive + `<retired>` name prefix
`create_process_step`, `update_process_step`, `delete_process_step`	Step CRUD with compile validation on code snippets
`create_process_trigger`, `update_process_trigger`, `delete_process_trigger`	Trigger management
`create_webapp`, `update_webapp`, `create_webapp_version`, `publish_webapp`, `unpublish_webapp`, `delete_webapp`	WebApp lifecycle and `page_content`

Platform admin tools (Phase 4)

Tool	Notes
`create_platform`, `update_platform`, `update_platform_strategy`	Business platform CRUD; strategy uses section prefixes from platform strategy config
`upload_document`, `move_document`, `create_document_review`	Tenant document filesystem + review workflow
`mark_notification_read`, `delete_notification`	Scoped to current user notifications
`upload_platform_file`, `delete_platform_file`	Platform-scoped file namespace (`content_base64` for uploads)

Opt-in flags

Resource	UI setting	MCP gate
Integration execute	Integration → Executable by AI Agents	`execute_tenant_integration`
Process execute	Process edit → Executable by AI Agents	`execute_process`, `run_process_trigger`

Default for both flags is off.

Human in the loop

Destructive writes and execute_process should be preceded by request_human_input with kind: confirm in production workflows. The agent receives an explicit approved/denied result in the tool loop.