Additional restrictions specifically to MCP

Get Help
1

Hello Fibery Team :slightly_smiling_face:

We have teams with Editor access to our databases. They can create, edit, and delete entities manually.

Previously, some of these teams used MCP with Trello to create tasks, and now they would like to work with Fibery in the same way through Claude.

My concern is that manual actions and AI actions have very different levels of risk. I trust team members to delete an individual task manually when necessary. However, through Claude and MCP, they could accidentally make a bulk change or delete many tasks at once.

Is it possible for workspace admins to apply additional restrictions specifically to MCP access for members?

For example:

  • allow creating and editing entities through MCP, but prevent deletion;

  • limit the number of entities that can be deleted or changed in one operation;

  • require admin approval for large or potentially destructive actions;

  • allow members to use MCP only with selected databases or actions.

If a member accidentally deletes or changes a large number of entities through MCP, what is the recommended way to restore them? Would an admin have to recover every entity or field change individually through the audit log?

It would be very useful to have an additional admin-controlled safety layer for member accounts connected through MCP, separate from their normal permissions inside Fibery.

2

So far we are not going to restrict it, but provide options to redo things easily in case of damage. We are working on two things right now

  • Provide additional information in history how thing was changed (via MCP, via API, etc)
  • Allow batch selection and batch undo/restore for many operations (now it is possible, but very limited)
3

Thank you very much! It will be helpful :+1: :slightly_smiling_face: