admin-only

What admin-only does on Frontmcp

AI agents invoke admin-only to trigger actions in Frontmcp. 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 admin-only is rated High

The description does not specify the tool's actual action, only its access control restriction. Given the 'admin-only' designation and the context of sibling tools like 'admin_action' and 'admin-background-job', this tool likely performs privileged administrative operations. Without a clear description of the action, Execute is the most appropriate category given administrative tools typically trigger operations.

From the tool's definition 'A tool restricted to admin role (RBAC roles.any)' — the name 'admin-only' and admin-role restriction suggest privileged operations, but the description is uninformative about what the tool actually does.

Risk signalsAdmin/system-level operation

The rule that runs admin-only safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For admin-only, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "admin-only": {
      "limits": [
        {
          "counter": "admin-only_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about admin-only