Trusted execution

Keep business credentials out of the agent.

Gateway connectors authorize and execute operations on the Quasentra server. Each workspace can configure its own HTTPS API, read-only PostgreSQL or SMTP connector from Dashboard → Trusted Gateway; no platform-admin change is required.

1. Prepare the agent key

Create an API key that includes tool:execute and restrict it to the agent that owns the gateway action.

2. Create the connector

  1. Run the secured application once so its agent and tools appear.
  2. Open Dashboard → Trusted Gateway → Create connector.
  3. Select the registered agent and exact tool action.
  4. Choose HTTPS API, PostgreSQL read-only or SMTP email.
  5. Enter the allowlisted route/query/domain and its credential.
  6. Save and validate. Secret values are encrypted and are never displayed again.
Credential rotation: edit the connector and enter a new secret. Leaving secret fields blank keeps the existing encrypted value.

3. Call the server-side connector

result = security.execute(
    agent_id="billing-agent",
    session_id="billing-session-100",
    action="invoice.fetch",
    arguments={"route": "invoice_api", "path_params": {"invoice_id": "INV-100"}},
    idempotency_key="billing-fetch-INV-100-20260825",
)

Use await security.aexecute(...) in async tools. Use a unique business idempotency key for every intended side effect, and reuse it only when retrying the identical operation.

HTTPS API guide
Allowlisted routes, path parameters, query strings and JSON bodies.

PostgreSQL guide
Named read-only queries with positional parameters.

SMTP email guide
Encrypted mailbox credentials and recipient-domain restrictions.

Troubleshooting
Diagnose missing agents, denied actions and connector failures.

What Validate checks

Validate confirms the saved configuration, connector rules and encrypted credential integrity. It does not contact the remote API, database or mail server. Run one non-production staging call to verify DNS, firewall, TLS, login and service permissions.

What the backend enforces

  • Exact workspace, API key, agent, action and policy authorization.
  • Customer connector ownership and encrypted credential retrieval.
  • HTTPS route allowlists and internal-network URL rejection.
  • Named PostgreSQL SELECT/WITH queries in read-only transactions.
  • SMTP recipient-domain allowlists.
  • Timeout, at-most-once idempotency claim and secret redaction.

Security boundary

The agent must not retain a second direct credential or unwrapped client to the protected service. Run an allowed staging tool call to verify the remote service itself.