Setting Tool Permissions, Approvals, and MFA
G8KEPR lets you control exactly which MCP tools an AI agent can call, which calls require a human approval, and which sensitive tools demand a fresh multi-factor challenge. This guide walks through configuring per-tool permissions, approval-required flags, and TOTP requirements.
How tool permissions work
Every MCP tool your agents can reach is governed by role-based access control (RBAC). Instead of granting an agent blanket access to a server, you grant access tool by tool, scoped to a role. An agent only ever sees the tools its role allows.
Each tool can carry three independent controls:
- ▸Access — whether a given role may call the tool at all.
- ▸Approval required — whether a matching call pauses for human sign-off before it runs.
- ▸Step-up MFA (TOTP) — whether the caller must pass a fresh authenticator challenge for that call.
Set per-tool access by role
- 1.Open Settings → MCP Security → Tool Permissions.
- 2.Choose the role you want to configure (for example, a read-only analyst role or a full operator role).
- 3.Toggle access on for each tool the role should reach. Leave sensitive or destructive tools off by default.
- 4.Save. Changes apply to new tool calls immediately.
Start from least privilege. Grant read and search tools broadly, and enable write, delete, or spend actions only for the roles that truly need them.
Require approval on sensitive tools
Mark any tool as approval-required to route its calls into a review queue instead of executing them automatically.
- 1.On the tool's row, enable Approval required.
- 2.When an agent calls that tool, the request is held and surfaced to reviewers in the approvals queue.
- 3.A reviewer approves or denies; only approved calls proceed, and every decision is logged.
Approvals are ideal for actions that move money, change infrastructure, or touch customer data — the agent can still request them, but a human stays in the loop.
Require MFA (TOTP) for high-risk tools
For your most sensitive tools, add a step-up TOTP requirement so a valid session alone is not enough.
- 1.Enable Require TOTP on the tool.
- 2.The caller must supply a current code from their authenticator app when the call is made.
- 3.Codes are time-based and single-use, so a stale or replayed code is rejected.
Enrol an authenticator before enabling TOTP requirements, or agents acting on your behalf will be blocked from those tools.