create_api_token · QR Forge MCP server MCP: Risk & Policy

WHAT IT DOES

What create_api_token does on QR Forge MCP server

AI agents use create_api_token to create or update resources in QR Forge MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QR Forge MCP server environment.

WHY IT NEEDS A POLICY

Why create_api_token needs a policy

This tool creates authentication credentials (API tokens) that grant access to the QR Forge API. While token creation is technically reversible (tokens can be revoked or deleted), the creation act itself is a Write operation that modifies the authentication/authorization state of the system. The 'exactly once' phrasing indicates the secret is sensitive and high-value.

From the tool's definition Tool name 'create_api_token' and description 'Create a new API token. The full secret is returned exactly once.' indicate irreversible creation of credentials.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_api_token Rate-limited

create_api_token stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_api_token": {
      "limits": [
        {
          "counter": "create_api_token_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about create_api_token

What does the create_api_token tool do? +

Create a new API token. The full secret is returned exactly once. It is categorised as a Write tool in the QR Forge MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_api_token? +

Register the QR Forge MCP server MCP server in PolicyLayer and add a rule for create_api_token: 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 QR Forge MCP server. Nothing to install.

What risk level is create_api_token? +

create_api_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_api_token? +

Yes. Add a rate_limit block to the create_api_token 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 create_api_token completely? +

Set action: deny in the PolicyLayer policy for create_api_token. 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 create_api_token? +

create_api_token is provided by the QR Forge MCP server MCP server (jkolarov/qrforge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.