The effective catalogue is an intersection
Tool availability depends on identity, grants, connection state and the execution surface. For Tasks, the selected harness adds its capabilities and restrictions. A tool listed in the product inventory is not automatically available to every agent.
Filter tools before execution
The model receives the effective catalogue, with only the capabilities available in that context. Configuration pages show the underlying tools and connections. Inspect both the granted connection and the resolved catalogue when an expected action is unavailable.
Match permission to the actual effect
A label such as read or write is useful only if it reflects what the provider really does. Consider recipient, destination, resource scope and side effects. Approval-sensitive mail uses its own explicit review path; arbitrary connected tools must be assessed on their actual contracts.
Control the browser’s network access
Local networks are blocked by default. Enabling local access on the Browser connection allows requesting permission; domain, port and network filters still take precedence. On a new installation, Public sites allowed permits public HTTP methods and WebSocket without per-site consent. Existing installations retain their choices; in Per-site authorisation mode, public GET requests pass with default settings while writes and WebSocket require consent.
When offered, Always allow all sites remembers web consent for that agent across future destinations. Filters, explicit denials and separate local-network permissions still apply. Active, Blocked and On request Browser function modes remain a separate control.
Approvals and refusals are remembered per agent, access type and origin—protocol, domain and port. After an answer, the action must be retried: a form is not automatically submitted again. Approval cannot bypass a connection filter.
In Monitor → Remembered permissions, authorised users can inspect requests and answers, filter decisions and remove a choice so Galaris asks again. Management remains limited to manageable agents and connection permissions.
Configure the minimum useful scope
Start with the sources needed for one deliverable. Add write access only for an identified destination. Test a forbidden operation and an unavailable connection. Recheck the catalogue after changing a role, connection or Task harness.
Keep sensitive settings under administration
An active connection and conversation access are separate choices. Browser and Search allow conversation use on initialisation. Console SSH, Image, Mail and Multimedia require explicit activation of that mode in the tool catalogue; this does not disable their use in tasks. Your existing settings are preserved.
An enforced global setting cannot be overridden by a connection. Function rules distinguish enabled and denied capabilities; discovery happens after filtering. Conversational Tool availability is a separate choice from Task access.
Each agent can expose a unified MCP endpoint to external clients. A named token per client makes revocation practical. Clients receive that agent’s scope, not general administration rights.
Separate mandatory services from access choices
Galaris, Conversation, Memory and File Sharing are mandatory services with protected definitions and connections. Their function modes remain configurable under the applicable rights. This foundation bypasses neither document access nor context limits. Administrative inspections recheck their connection when called.
Document applications: each reader gives consent
A page may contain interactive code, but Dataset access is denied by default. The reader’s current rights to the page and data are combined with personal consent, given through Application permissions for that content version. Neither the code nor the authoring agent can grant this access to itself.
Consent does not transfer to another reader or document. Editing or restoring content requires new consent; changing only the title does not. Revocation blocks subsequent calls without removing data already read or undoing completed writes.
Write access allows appending and full replacement, potentially as soon as the page opens. Review sources and destinations together: an authorised application can move data between Datasets. Isolation blocks direct access to the parent DOM, Galaris cookies and storage, and ordinary network loads. It does not cap JavaScript CPU or memory consumption.
Use documents and their applications
Approve once or remember consent
For an On request function, the manager receives a localised question and can inspect arguments before approving or refusing. When offered, Always allow this function activates only that function on that connection, including its future arguments. This option does not apply to local harness commands. Rights, revocations and resource preconditions are still checked on continuation.
The Permissions page can resolve requests even without an available private channel. An expired or duplicate answer does not cause a second operation. A source changed after approval can block the action; an uncertain external outcome requires reconciliation. Prepare team connections.


