Hello everyone,
I am looking for some help with an Agent - Context: We have a HubSpot tool restricted to only a few team members, because it has write access to our HubSpot account.
We then created an agent using this MCP tool and clearly stated in the prompt that it should not mutate data in HubSpot to ensure that users won’t change data in HubSpot via the agent. When we publish it, its availability is restricted to the users who have access to the tool. Our goal is to restrict access to the tool but not the agents using it. Is that possible?
Many thanks
Thank you for posting to the Community!
I’d like to tag in some of our Subject Experts to take a look -- @gabriel-nextiny and @DGarg Do you have any ideas for @Akent1?
Cassie, Community Manager
Could actually spell out each tool by name what exactly you have set up? You mention “HubSpot Tool”, “MCP Tool” and “the tool” - hard to follow which is which and what they are supposed to be doing.
Sure Betreff
HubSpot has an MCP which is one of the tools we can integrate with via Dust. Does that make sense? If yes, then this will too - I have now created an agent called HubSpot off the back of the hubspot tool but the tool (MCP) is restricted on a company level because of its ability to mutate data.
Our thinking was - restrict the MCP > create a public agent where we have embedded into its instructions “Do not mutate data” then make that agent public.
Our findings- the agent is still restricted because it core source (MCP tool) is restricted.
How can we move forward?