reactivate_user · Kula Ai MCP: Risk & Policy

WHAT IT DOES

What reactivate_user does on Kula Ai

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

WHY IT NEEDS A POLICY

Why reactivate_user needs a policy

This tool restores a deactivated user account, which is a reversible state change (Write). It modifies user status but does not create new data or irreversibly destroy anything. Misuse could grant system access to unintended individuals, hence medium severity.

From the tool's definition Reactivate a previously deactivated user

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reactivate_user Rate-limited

reactivate_user 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": {
    "reactivate_user": {
      "limits": [
        {
          "counter": "reactivate_user_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 Kula Ai, so you can run agents against it safely.

FAQ

Questions about reactivate_user

What does the reactivate_user tool do? +

Reactivate a previously deactivated user. It is categorised as a Write tool in the Kula Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reactivate_user? +

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

What risk level is reactivate_user? +

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

Can I rate-limit reactivate_user? +

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

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

reactivate_user is provided by the Kula Ai MCP server (kula-ai/kula-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.