Enhancing MCP Server Security: Tool Access Restrictions Proposal

Hi everyone, thanks for the MCP server addition feature - it's a complete game-changer for using Dust agents. I have a suggestion for an improvement that would greatly enhance security in MCP server management. For certain external servers, we can have a set of tools that allow reading, updating, writing objects, etc. We can currently configure confirmation requests and action management in "Tool stake settings" to increase security. It would be great if we could also block an agent from using a specific tool - for example, to prevent accidentally deleting a CRM contact. I realize that creating guardrails through agent text prompting isn't 100% reliable, so it would be much more effective and secure to be able to restrict tool access at the MCP server settings level. What do you think?