Is it possible to have an Automation only use spec...
# proj-automation
e
Is it possible to have an Automation only use specific MCP servers, secrets, plugins, skills, LLM profiles? That is, narrowly scope the Automation to only have access to specific resources. Wondering if this is supported today or would need to be an enhancement
Use case: I want to control exactly what the automation has access to within the scope of it's current configuration environment. This may help me limit the blast-radius of the automation.
nod 1
c
I believe that's what Agent Profiles will be best at. I'd make two notes: • I'm not sure it's possible today, at least in the UI it's not (cc @strong-ice-84145 ) • the introduction of Agent Profiles is new, and we currently have a bit of confusing UX with LLM Profiles and how they should work. (making a different issue on this)
nod 2
e
agree with the UX confusion, I think Devin is looking into it (related: github.com/OpenHands/agent-canvas/issues/1888)
thanks on a stick 1
good to know Agent Profiles might help here!
l
Yeah, this is the use case for agent profiles, but we need to make it better documented and supported!