projects_rename

Run projects.rename through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/projects-rename.md

WHAT IT DOES

What projects_rename does on Appaloft

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

Parameter	Type	Required	Description
`name`	string	Yes
`projectId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why projects_rename is rated Medium

Renaming projects is a reversible modification that creates side effects by altering project metadata. This fits the Write category (creates or modifies data reversibly). Severity is medium because project name changes could affect workflows, integrations, or user experience, but the impact is typically recoverable and localized to project identity/metadata rather than destructive data loss or financial consequences.

From the tool's definition Tool name 'projects_rename' and description 'Run projects.rename' indicate modification of project data. The description states it operates through 'application operation catalog' shared with CLI and HTTP/API, confirming it performs state changes rather than…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs projects_rename safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For projects_rename, this is the rule to start with:

projects_rename Rate-limited

projects_rename 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": {
    "projects_rename": {
      "limits": [
        {
          "counter": "projects_rename_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every projects_rename call is checked against it from then on.

FAQ

Questions about projects_rename

What does the projects_rename tool do? +

Run projects.rename through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does projects_rename accept? +

projects_rename accepts 2 parameters: name, projectId. Required: name, projectId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on projects_rename? +

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

What risk level is projects_rename? +

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

Can I rate-limit projects_rename? +

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

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

projects_rename is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 358 Appaloft tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →