rename_project · Run402 MCP: Risk & Policy

WHAT IT DOES

What rename_project does on Run402

AI agents use rename_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 rename_project needs a policy

This tool creates or modifies data reversibly by changing a project's name via PATCH request. It does not delete, destroy, or execute arbitrary code—just updates a project attribute. The authorization model (org-membership or project:write grant) provides some protection. Severity is medium because an attacker could rename projects to cause confusion or disrupt workflows, but the change is reversible.

From the tool's definition Tool description states it performs a PATCH operation to rename a project, which modifies project metadata reversibly.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_project Rate-limited

rename_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": {
    "rename_project": {
      "limits": [
        {
          "counter": "rename_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 rename_project

What does the rename_project tool do? +

Rename a project (PATCH /projects/v1/:id) — fix an auto-generated name. Authorization is org-membership based (admin+ on the owning org, or a project:write grant) and authorize-before-reveal: an unauthorized or guessed id returns the same 403 as a real-but-unauthorized project, never a not-found oracle. Uses the wallet. 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 rename_project? +

Register the Run402 MCP server in PolicyLayer and add a rule for rename_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 rename_project? +

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

Can I rate-limit rename_project? +

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

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

rename_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.