StackJack 0.1.0.12125+a9570fd
StackJack 0.1.0.12125+a9570fd
Tool roles can now be limited to a single connection of a connector, and a role rule can grant a hand-picked set of tools rather than the whole connector. This gives you finer control when you have several connections to the same tool, for example one per client.
New features
- Connection-scoped role rules. Each connector rule in the Roles editor now has a Connection picker. You can apply the rule to all connections, which is how existing rules behave, or to one named connection. When a role names a specific connection, everything that role grants on that connector applies only on that connection.
- Specific tools per rule. A connector rule can now grant a chosen set of tools. A tool picker lists the tools available for that connector.
- AI agents follow connection rules. Agents are held to these rules on every request:
- If a caller is allowed exactly one connection, that connection is used automatically.
- If a caller is allowed several connections, the agent must name the one it wants.
- If a caller is allowed none, the connector is unavailable to them.
- Agents only see the connections they are allowed to use. This applies to connection lists and connection choices.
- A tool call is refused if that tool is not allowed on the chosen connection.
- Personal sign-ins follow connection rules. Members can't start or complete a personal sign-in for a connection their roles don't allow.
- Exemptions. Owners, co-owners and administrators are never limited by connection rules.
Improvements
- Endpoints. An endpoint's roles apply to that endpoint no matter who owns it. When a member works through an endpoint, they get only the access that both the member's roles and the endpoint's roles allow, checked for each connection.
- Automations. If an automation is bound to a connection that its run-as user's roles don't allow, the connector is closed for that automation, including for health checks. A new support code explains why. It is listed on the support-code reference page.
- Responses name the connection. When a caller is allowed only one connection, responses state which connection handled the call.
- Clearer refusals for pinned connections. An endpoint pinned to a connection that its roles forbid now gets a plain refusal.
- Live tool test in the builder. The live tool test follows connection rules. It runs on the same connection that was checked.
UI & UX changes
- Rule pills. Rule pills in the Roles editor show the connection name when a rule is limited to one connection.
- Removed connections. A rule that points to a connection that no longer exists is badged, and the editor shows a warning.
- Ineffective rules. A specific-tools rule that has no effect is highlighted.
- Connection names on the Roles page. Only people who can manage roles see connection names on the Roles page.
- Autotask identity card. The Autotask identity card in personal sign-ins lists only the connections the member's roles allow.
- Documentation. The roles help page has been updated to cover connection rules.