admin_reactivate_project · Run402 MCP: Risk & Policy

WHAT IT DOES

What admin_reactivate_project does on Run402

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

WHY IT NEEDS A POLICY

Why admin_reactivate_project needs a policy

This tool reverses an archived state, making it a write/update operation (restoring a project). It is the inverse of archiving, not a destructive action. The description is truncated ('flips'), which limits confidence, but the intent appears to be toggling a project back to active status — a reversible state change.

From the tool's definition admin_reactivate_project — 'Operator un-archive — flips'

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

admin_reactivate_project Rate-limited

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

FAQ

Questions about admin_reactivate_project

What does the admin_reactivate_project tool do? +

Operator un-archive — flips. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on admin_reactivate_project? +

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

What risk level is admin_reactivate_project? +

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

Can I rate-limit admin_reactivate_project? +

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

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

admin_reactivate_project is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.