A lookup assistant can use PD MCP Hub without being allowed to change records. Use the connection’s Ceiling and its separate read-only switch together when the task is strictly informational.

Choose the connection you intend to restrict

Open PD Modules → MCP Hub → Connections. Give each assistant its own recognisable connection name so you can change one assistant’s access without changing another’s.

If you are creating the first connection, use Create a connection, select the active Blesta staff account with the appropriate staff-group permissions, and copy the new token when it is shown. Use Connect for this installation’s endpoint. Keep the token in the assistant’s credential settings, never in the URL.

Apply the read-only controls

1. Choose Edit on the intended connection.
2. Set Ceiling to Read only — look things up, change nothing.
3. Tick Read only, whatever else is set — a hard stop that outranks the ceiling.
4. Under Which areas it can reach, retain only the areas needed for the lookup task.
5. Review the selected staff account and any client limit, then choose Save changes.

The separate checkbox continues to prevent changes if somebody later raises the ceiling. Unticking it does not itself grant write access: the ceiling and staff permissions still apply. Requiring approval for changes is different from preventing changes altogether.

Check the result

Refresh or reconnect the assistant so it obtains the current tool list. Check that the expected read tools remain available, then inspect Audit trail for the connection and any refusal. Reading a client record still requires the relevant permission and client scope; read-only does not mean unrestricted access to records.

Editing a connection keeps its token. You do not need New token merely to narrow permissions. If an expected read is refused, identify the specific area, staff permission or client restriction before changing anything else.

See the PD MCP Hub Blesta guide for related tasks, or explore PD MCP Hub.