Royal MCP and Royal AI Firewall together
Royal MCP lets AI agents work with your site. Royal AI Firewall decides which AI bots get in. Together, your own Royal MCP connections keep working whatever you block, and every Royal MCP tool call shows up on the firewall's dashboard. This page explains how.
Royal AI Firewall 1.0.12 or later. Tool-call recording needs Royal MCP 1.4.33 or later (Free or Pro). Abilities API logging needs WordPress 6.9 or later.
Do bot policies apply to MCP requests?
Not to your Royal MCP connections. A request to Royal MCP's endpoint that carries an Authorization header is treated as your own AI client, so the firewall lets Royal MCP handle it. Royal MCP checks the credentials and refuses the request when they are wrong. This holds even under Block all AI bots except verified search engines.
- Royal MCP endpoint, with an Authorization header: never blocked, rate limited or paywalled by the firewall. Royal MCP then checks the token.
- Royal MCP endpoint, without an Authorization header: checked like any other request. Royal MCP refuses it anyway.
- Other MCP servers and other REST routes: checked by user agent like a page request. If the client sends a user agent from the bot catalog (Claude Code sends
claude-code), that bot's policy applies.
If its client stops connecting after you turn on blocking, open AI Firewall → Activity Log and look for 403 rows on that server's endpoint. Set that bot to Always allow on the dashboard. A per-bot policy always wins over the default policy.
How Royal MCP tool calls are recorded
After each tool call, Royal MCP tells the firewall which tool ran and whether it succeeded. The firewall stores that as a log-only record: the tool has already run, so the record is a history of the call, not a decision about it.
- The record keeps the tool name, success or error, the time, and the caller's IP address and user agent.
- If the client's user agent is in the catalog, the call is filed under that bot. Otherwise it is filed under Unknown MCP client.
- Tool arguments and results are not stored.
- These records follow the normal log retention window.
What the MCP / Abilities API activity widget shows
The widget appears on the AI Firewall dashboard when Royal MCP is active, or when any tool or ability call was recorded in the last 24 hours. It shows:
- the 20 most-called tools and abilities in the last 24 hours, each with its call count, an error count when calls failed, and its source (
mcp-serverfor Royal MCP,abilitiesfor the Abilities API) - a total: the sum of those 20 rows
- a note saying whether Royal MCP is installed
Tool and ability calls are counted only in this widget. They are kept out of the per-bot list and hit totals, so your AI bot numbers show crawler traffic only. The MCP HTTP requests themselves are a different matter: when the client's user agent is in the catalog, those requests also appear in the per-bot list like any other request.
Abilities API logging
On WordPress 6.9 and later, other MCP server plugins can expose site actions through the WordPress Abilities API. The firewall covers those calls in two ways:
- Calls over the REST API, including MCP transports, are checked and logged by the firewall as normal requests when the caller's user agent is in the catalog.
- Calls made outside a REST request by a recognized AI bot are recorded at the ability level and shown in the activity widget with the ability's name.
Calls from WP-CLI, cron and other internal code are not logged; they are not AI traffic.
Still stuck? Two support paths
Community support (free): wp.org plugin forum
Post a new thread at wordpress.org/support/plugin/royal-ai-firewall/. The Royal Plugins team monitors the forum regularly.
Premium support (paid)
For direct one-on-one help with a 24-hour SLA, see Premium Support ($149/year).
Information to include (either path)
- Your Royal AI Firewall and Royal MCP versions
- The AI client you connect with (Claude Code, Claude Desktop, ChatGPT, Cursor and so on)
- The policy for that bot and your default policy
- The status code your client receives, and any matching rows in the Activity Log