environments_rename
Run environments.rename through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/environments-rename.md
What environments_rename does on Appaloft
AI agents use environments_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 | |
environmentId | string | Yes |
Parameters from the server's own tool schema.
Why environments_rename is rated Medium
Renaming environments is a reversible write operation that modifies configuration state without deletion. This affects infrastructure or application environment settings, making it high severity if misused by an agent (e.g., renaming production environments). The tool is Write rather than Execute because it performs a specific data mutation rather than arbitrary code execution.
From the tool's definition Tool name 'environments_rename' indicates modification of environment names. Description states it 'Run environments.rename through the Appaloft application operation catalog', confirming it performs a rename operation (modification of data).
Attacks that exploit this kind of access
The rule that runs environments_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 environments_rename, this is the rule to start with:
environments_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every environments_rename call is checked against it from then on.
Questions about environments_rename
Run environments.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.
environments_rename accepts 2 parameters: name, environmentId. Required: name, environmentId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for environments_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.
environments_rename is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the environments_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.
Set action: deny in the PolicyLayer policy for environments_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.
environments_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.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue