MCP Permissions

Balanced, Full Automation and Cautious provide starting policies for operation types.

Full Automation reduces approval interruptions; Cautious asks or blocks more host-sensitive operations. Choose the preset that matches how much you trust the connected AI client.

Allow executes the operation type without asking. Ask creates an approval request. Block refuses the operation.

Policies apply to the operation type, so review broad capabilities such as filesystem, desktop capture, process control and browser administration carefully.

The fallback policy decides what happens when an operation requires approval but the user is not available. Failing the operation is safer than silently widening permissions.

Pending approvals can be approved once, allowed for a limited period, allowed always or denied for the operation type.

Temporary grants show time-limited authorizations created by approval actions. Review them when diagnosing why an operation no longer asks for approval.

MCP authorization is a real browser/host security boundary. Use the least-permissive policy that still lets the intended automation run reliably.