---
title: "MCP security and access"
description: "How MazeGraph protects an MCP connection: administrator-only access, passwords that work only on the MCP address, rate limits, Activity records and multisite rules."
image: "https://mazegraph.com/docs/og.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://mazegraph.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP security and access

Opening your site to an outside app is a real decision, so MazeGraph keeps the MCP server narrow: read-only, administrators only, and checked on every request.

## Who can connect

Only people who can manage the site (the WordPress `manage_options` capability, which administrators have) can turn the server on, create connections and connect. A connection signs in as the administrator who created it. If that person loses administrator rights, their connections stop working.

## Connection passwords

A connection is a WordPress Application Password that MazeGraph creates and tags as its own. MazeGraph refuses it everywhere except the MCP address, so a leaked key cannot read or change the site through the rest of the WordPress REST API. Your other Application Passwords are not affected.

- The key is shown once, when you create or regenerate it. WordPress stores only a hash.
- Each connection shows when it was **Created** and **Last used**.
- Deactivating or deleting MazeGraph revokes every MCP connection.

If MazeGraph stops running without being deactivated, for example when WordPress recovery mode pauses it after an error, or its folder is removed by hand, nothing limits these passwords to the MCP address any more. Revoke them under **Users → Profile → Application Passwords** if MazeGraph will stay off.

## Checks on every request

Before an MCP request reaches a tool, MazeGraph checks:

1. **Origin.** A request from a web page on another site is refused, which blocks attacks that use your browser.
2. **Sign-in and role.** The request must carry a valid connection password for an administrator.
3. **Rate limit.** Each account may send 120 requests a minute; a batch counts each request in it. Over the limit, MazeGraph's own server answers `429 Too Many Requests` with a `Retry-After` header.
4. **Policy.** The same policy that guards the chat decides each tool call. It refuses anything but the read-only tools listed in [Tools available over MCP](/docs/mcp/tools-available-over-mcp/), and no call can carry an approval.

These checks run the same way whether MazeGraph's own server or the MCP Adapter answers.

## What is recorded

Every call made through MazeGraph's MCP connection endpoint appears in **MazeGraph → Activity → Plugin logs** with an MCP badge; use the **From MCP** filter to see only these. A record holds the tool, its status, the time taken and the size of the result, never the arguments or the result itself. The separate WordPress MCP Adapter default Ability server does not use this Bridge record; see the sharing-switch note below.

Requests refused before a tool runs are recorded as denials with a code:

| Code | Meaning |
| --- | --- |
| `mcp_auth_failed` | A wrong, revoked or misplaced password. |
| `mcp_auth_required` | No password was sent. |
| `mcp_forbidden` | The account is not allowed to connect. |
| `mcp_rate_limited` | The account went over its limit. |
| `mcp_tool_unavailable` | The tool is unknown, switched off, outside its supported surface, or otherwise unavailable. |

Each kind is recorded at most once a minute, so a flood of bad requests cannot fill the log. No password, header or IP address is stored. Wrong passwords are not rate-limited by MazeGraph, as in WordPress core; watch for repeated `mcp_auth_failed` records.

## Multisite networks

WordPress keeps Application Passwords for the whole network, not one site. So on a multisite network, MazeGraph offers MCP connections only when it is network-activated, and a connection works only on the site where it was made.

## The MCP Adapter sharing switch

**Share read-only tools with MCP apps**, under **MCP sharing** on the MCP screen, is a separate option for the MCP Adapter's default WordPress Ability server. It marks eligible read-effect MazeGraph abilities as public when they are switched on and have the MCP surface. These direct Ability calls still run the ability permission callback and MazeGraph's DirectCallGuard policy check. They do not use the MazeGraph MCP Bridge's normal tool-execution audit record. Use the MazeGraph-managed MCP server above when you want the complete MCP connection and Activity path. Neither MCP path can run a write tool or accept an approval from an outside app.

Source: https://mazegraph.com/docs/mcp/security-and-access/index.mdx
