Description
Might be a role limitation -- as in needing a broader range of roles within RBAC -- but the current perms on the MCP are a little terrifying for Admin users. Specifically the ability to modify schemas, which could pretty easily mess up the underlying frontend of the site if you didn't know what you were doing.
Even as an Admin who knows (relatively) what he's doing, I'd want less perms for my agent, just in case something goes wrong.
Potential solution could be adding ability to customize the perms around the MCP server, so it doesn't automatically get all of your access as a user.
Steps to reproduce
n/a
Environment
n/a
Logs / error output
Description
Might be a role limitation -- as in needing a broader range of roles within RBAC -- but the current perms on the MCP are a little terrifying for Admin users. Specifically the ability to modify schemas, which could pretty easily mess up the underlying frontend of the site if you didn't know what you were doing.
Even as an Admin who knows (relatively) what he's doing, I'd want less perms for my agent, just in case something goes wrong.
Potential solution could be adding ability to customize the perms around the MCP server, so it doesn't automatically get all of your access as a user.
Steps to reproduce
n/a
Environment
n/a
Logs / error output