activate_license · Creem MCP: Risk & Policy

WHAT IT DOES

What activate_license does on Creem

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

WHY IT NEEDS A POLICY

Why activate_license needs a policy

This tool creates or modifies data reversibly—activating a license changes its state but is not irreversible (a license can be deactivated). It does not execute arbitrary code, delete data, or move money directly. While it affects licensing/access control, the action itself is a reversible state change, making it Write category rather than Execute or Destructive.

From the tool's definition Tool description states 'Activate a license key' which is a state-changing operation that modifies license status. The Creem.io context (managing subscriptions, products, payments, license keys) confirms this operates on financial/licensing infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

activate_license Rate-limited

activate_license 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": {
    "activate_license": {
      "limits": [
        {
          "counter": "activate_license_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 Creem, so you can run agents against it safely.

FAQ

Questions about activate_license

What does the activate_license tool do? +

Activate a license key for a specific instance/device. It is categorised as a Write tool in the Creem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on activate_license? +

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

What risk level is activate_license? +

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

Can I rate-limit activate_license? +

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

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

activate_license is provided by the Creem MCP server (selenium39/mcp-server-creem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.