environments_duplicate_profile
Run environments.duplicate-profile through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/environments-duplicate-profile.md
What environments_duplicate_profile does on Appaloft
AI agents invoke environments_duplicate_profile to trigger actions in Appaloft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
targetKind | string | — | |
targetName | string | Yes | |
environmentId | string | Yes | |
resourceDecisions | array | — | |
dependencyDecisions | array | — | |
dependencyKindsToRequire | array | — |
Parameters from the server's own tool schema.
Why environments_duplicate_profile is rated High
The description uses 'Run' indicating execution of an operation via an application catalog. Duplicating a profile likely creates a new environment/profile (Write-level side effect), but the 'Run ... operation catalog' framing suggests execution of a potentially complex operation with broader side effects.
From the tool's definition 'Run environments.duplicate-profile through the Appaloft application operation catalog'
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs environments_duplicate_profile 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_duplicate_profile, this is the rule to start with:
environments_duplicate_profile stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_duplicate_profile call is checked against it from then on.
Questions about environments_duplicate_profile
Run environments.duplicate-profile through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
environments_duplicate_profile accepts 6 parameters: targetKind, targetName, environmentId, resourceDecisions, dependencyDecisions, dependencyKindsToRequire. Required: targetName, 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_duplicate_profile: 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_duplicate_profile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the environments_duplicate_profile 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_duplicate_profile. 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_duplicate_profile 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.
Across the catalogue