wiki_auth_set_api_state · Mcp Wikijs Mv MCP: Risk & Policy

WHAT IT DOES

What wiki_auth_set_api_state does on Mcp Wikijs Mv

AI agents invoke wiki_auth_set_api_state to trigger actions in Mcp Wikijs Mv. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why wiki_auth_set_api_state needs a policy

This tool toggles the global state of the GraphQL API for the entire Wiki.js instance. Disabling it would cut off all API access for all users system-wide — a highly impactful, reversible but operationally severe action. It doesn't delete data (so not Destructive), but it triggers a system-wide operational change that could deny service to all users, making it Execute at critical severity.

From the tool's definition Enable or disable the Wiki.js GraphQL API globally

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wiki_auth_set_api_state Rate-limited

wiki_auth_set_api_state stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wiki_auth_set_api_state": {
      "limits": [
        {
          "counter": "wiki_auth_set_api_state_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Wikijs Mv, so you can run agents against it safely.

FAQ

Questions about wiki_auth_set_api_state

What does the wiki_auth_set_api_state tool do? +

Enable or disable the Wiki.js GraphQL API globally. It is categorised as a Execute tool in the Mcp Wikijs Mv MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wiki_auth_set_api_state? +

Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_auth_set_api_state: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Wikijs Mv. Nothing to install.

What risk level is wiki_auth_set_api_state? +

wiki_auth_set_api_state is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wiki_auth_set_api_state? +

Yes. Add a rate_limit block to the wiki_auth_set_api_state rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block wiki_auth_set_api_state completely? +

Set action: deny in the PolicyLayer policy for wiki_auth_set_api_state. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides wiki_auth_set_api_state? +

wiki_auth_set_api_state is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.