Agent Compute lets a Files.com Automation request work from a program inside your environment. That program may have access beyond the folder exposed for file transfers. The central approval decision is what the program can do with every input the workflow may supply.

Approving a Local Capability

The host administrator defines the executable, argument templates, and parameter schema in the Agent configuration. The Automation selects a configured command name and supplies parameter values. With no command definitions, the Agent rejects every Agent Compute command.

This separates command approval from workflow authoring. An Automation author can use an approved capability without editing the host configuration, but the approved program determines how broad that capability is.

For example, a command that processes one file in an exchange folder is narrower than a general interpreter accepting arbitrary command text. Giving both definitions a descriptive name does not make their authority equivalent.

Review who can author or change Automations using the Agent, and what those authors can cause each command to do. Include inputs derived from incoming files, external events, and earlier workflow results in that review.

Inputs Must Remain Within the Intended Work

The Agent starts the configured executable directly and supplies its arguments. It does not implicitly run every definition through a shell. The executable decides whether an argument is ordinary data, a path, an option, or instructions to execute.

Keep the executable and script path fixed, and pass values as separate data arguments. Have the program validate allowed operations, paths, and options before performing work. A parameter's string type does not restrict it to an approved directory or establish permission to select a particular customer's data.

If a script evaluates incoming text as instructions or constructs another command from it, separated arguments alone do not limit the result. Review the called scripts and programs as part of the approved capability.

For POSIX shell command text, use the Agent's shellquote function as described in Scripts and Input Values. Its quoting rules do not apply to PowerShell or cmd.exe.

The Agent's startup validation catches some missing quoting in recognized command templates. Passing that validation does not establish that all inputs are safe or that the program performs only the intended operations.

Operating-System Authority

Programs run with the operating-system permissions of the Agent account. The file-transfer root and read_only setting do not confine them, and a command's working directory does not limit which files it can access.

A Files.com Workspace limits the platform resources available to a workflow. It does not impose matching restrictions on local files, credentials, or internal services used by the program.

Use a service account with only the authority the approved work requires. Separate workloads when they need independent local permissions, and protect executable files, scripts, configuration, and their parent directories from changes by workflow authors or uploaders who should not control the program.

Results and Repeated Work

Standard output and standard error return to Files.com as Automation data. Print only the results the workflow needs; local credentials or confidential file contents printed by the program become part of that returned data.

Plan how the program handles partial completion and repeated requests. A workflow failure does not undo files changed or messages sent by a program that already ran. Confirm the result in the system where the operation occurs before repeating work with consequential effects.

For high availability, approve and deploy the same intended commands on every host that can serve the Remote Server. Review the permissions and program contents on each host; a matching command name alone does not establish consistent behavior.