PolyAccounts · Developer evaluation
Agent access and accounting controls
Full agent read and write access with company isolation, administrator-issued credentials, revisions, durable idempotency and accounting controls.
Agents can do the accounting work
The recommended connector grants read, create, update and soft-delete access to supported company records, together with accounting workflow execution. It is not restricted to analysis. Discover the current tools and operation schemas instead of assuming every table accepts every generic write.
Examples include maintaining ledger records, managing supported reference data, posting invoices, recording payments, reconciling and managing periods through the appropriate workflows. The public tool catalog is generated from the server’s tools/list response.
The company boundary remains in force
An administrator issues each credential for one company. Requests are attributed to that credential and operate within its company boundary. Credentials can be revoked. A model does not get unrestricted database access or permission to cross into another customer’s records.
Full access is powerful. Issue a credential only to a client you intend to authorize for that company. This connection is a company-scoped accounting capability, not a promise of per-tool permission scopes or an OAuth consent experience.
Writes retain accounting controls
Durable idempotency receipts help a client determine whether a requested operation already happened. Revision checks reject stale edits. Soft deletion preserves ledger history. These mechanisms remain in force when an agent acts.
Posting, approval and period controls still apply. Invoice payments must use billing payment actions so invoice balances, history and ledger entries stay aligned. Stripe payment reversals require a verified provider refund. Generic database writes are not a replacement for those workflows.
A separate legacy connection
The older direct PostgreSQL MCP connection remains read-only. Company-locked structured queries and raw SQL restrictions apply to that operator connection. It is not the recommended onboarding path for new agent integrations.
The standalone synthetic demo also remains read-only and contains only invented data. To evaluate full accounting writes, use the hosted connector with an administrator-approved synthetic workspace.