Skip to content

Policy Administration and Safeguards

Updated View as Markdown

MazeGraph’s free version makes a separate decision for each reply and tool action. Site settings set the boundaries, MazeGraph’s policy checks apply them, and WordPress decides what the signed-in person is allowed to do. The AI model cannot switch on a tool, grant itself a capability, or talk its way around a refusal.

This page explains how those checks fit together. For the full rule order and the session approval modes, see How MazeGraph decides what may happen and Approval modes.

Policy is MazeGraph’s decision process. It checks whether a request can proceed, must wait for a person’s approval, or must be refused. Permissions are one part of that decision: they check whether the selected assistant, the site’s tool settings, and the current WordPress user allow a particular tool.

These checks use the real WordPress account behind the session. MazeGraph does not give the model a separate administrator account. A person may be able to chat and still be unable to use a particular tool, because WordPress checks each tool against that person’s capabilities.

Workspace access is separate from tool access. By default, MazeGraph is available to WordPress administrators, but an administrator’s account still does not bypass a tool’s individual checks. See Availability and role access.

How MazeGraph checks an action

When a reply uses a tool, MazeGraph runs its checks in a fixed order. A failed check stops that action; an approval requirement stays in force through the later checks.

Check What MazeGraph looks at What happens when it does not pass
Guardrails Whether new replies are allowed, the person has accepted the data notice, usage limits remain, and a requested write is safe and undoable. The reply or action is refused, or the tool call waits for approval. A later setting cannot override the result.
Additional policy rules Rules supplied by MazeGraph definitions, a compatible plugin, or the active theme. A rule can match an action and a tool. A deny refuses the match. An ask pauses a matching tool call for approval of its exact arguments. These rules can tighten access, never grant it.
Tool permissions Whether tool use is allowed site-wide, the individual tool is enabled, the selected assistant includes it, and the current person passes the tool’s WordPress permission check. The tool is unavailable to that person. If no permission allows the action, MazeGraph denies it by default.

The order matters. For example, selecting Full approval mode cannot override a daily limit, a disabled tool, a policy denial, or a WordPress capability check. A rule that asks for approval also keeps that requirement even when the session mode would otherwise skip an approval prompt.

Site controls and where to find them

The administrator sets broad limits in MazeGraph → Settings. Individual tool switches live in MazeGraph → Tools.

Control What it governs
Settings → General → Allow new replies Stops new requests to the AI provider across the site. Existing sessions remain readable.
Settings → General → Allow tool use Removes tools from chat across the site. It does not change the individual tool switches.
MazeGraph → Tools → Tools Enables or disables eligible tools. A tool still has to pass its assistant and WordPress permission checks.
MazeGraph → Settings → Tools → Give the main assistant access to all enabled tools Lets the built-in main assistant consider all enabled tools. It does not change other assistants’ tool lists or bypass policy.
MazeGraph → Settings → Limits and privacy Sets reply length and step limits, the shared daily token allowance, and the per-person message pace.
MazeGraph → Tools → Extensions Shows registered definitions, including any policy rules supplied by the site or an extension.

For details on the tool catalogue and assistant scopes, see Tools, Agents, and Extensions. For the settings themselves, see General settings, Tool settings, and Limits and privacy.

Example: a tool is on, but WordPress still refuses it

Suppose an editor can open MazeGraph and asks how many user accounts each role has. The Count users tool may be enabled and included in the selected assistant, but the tool also checks the WordPress list_users capability for the person who made the request. If WordPress does not grant that capability, MazeGraph refuses the tool call. Changing from Ask to Full does not grant access; a WordPress administrator must decide whether that person should have the capability.

This separation prevents workspace access from becoming broad WordPress access. The same principle applies to tools that inspect settings, plugins, scheduled events, or other protected parts of the site: each tool checks the permission WordPress requires for that task.

Example: a write needs both access and policy approval

MazeGraph’s write tools start off disabled. For an assistant call, the selected tool must be enabled and included in the assistant’s scope; the current person must pass its WordPress permission callback; and policy must allow the exact action. With Ask selected, MazeGraph shows the proposed change and waits for approval of the exact call. Auto skips that prompt only for marked common draft operations. Full can skip it for supported undoable writes when policy allows. Site content in the conversation or a stricter policy rule can still require approval in any mode.

Approval does not publish a post. Draft tools create or update drafts; other tools can move content to the trash, edit media text or terms, or update WooCommerce data. In particular, updating a published product changes the live shop immediately. An order status change may trigger configured customer email, and undo cannot unsend an email. Supported writes are recorded and can be undone where the handler’s conditions still hold.

If the tool is disabled or WordPress denies the person’s permission, no approval prompt can make the action proceed. Full does not bypass limits, denials, WordPress permissions, or undo requirements. A person’s own Save or Import action is itself their approval and still passes the same final policy and permission checks. See Who may use tools, Approval modes, and Review changes and undo.

Policy rules can add another boundary

A policy rule can target an action such as using a particular tool. For example, a site rule could deny draft creation entirely, or require a person to approve a matching call even when the session is in Auto or Full mode. The rule cannot grant access that WordPress or another MazeGraph check has denied.

Definitions are reviewed in MazeGraph → Tools → Extensions. They may come from MazeGraph, a plugin, the active theme, or a definition stored on the site. See How MazeGraph decides what may happen for the detailed check order and A tool is missing or refused for help diagnosing a blocked action.

Was this page helpful?

Your feedback helps us improve these docs.

Documentation

Type to search…

↑↓ navigate↵ selectEsc close