environments_create
Run environments.create through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/environments-create.md
What environments_create does on Appaloft
AI agents use environments_create 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 |
|---|---|---|---|
kind | string | Yes | |
name | string | Yes | |
projectId | string | Yes | |
parentEnvironmentId | string | — |
Parameters from the server's own tool schema.
Why environments_create is rated Medium
This tool creates new environments within the Appaloft application. Creation operations are Write-category actions because they modify state but are typically reversible (environments can be deleted or modified later).
From the tool's definition Tool name is 'environments_create' and description states it is an application operation that creates entities. The 'create' verb indicates reversible data modification.
Attacks that exploit this kind of access
The rule that runs environments_create 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_create, this is the rule to start with:
environments_create 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_create call is checked against it from then on.
Questions about environments_create
Run environments.create 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_create accepts 4 parameters: kind, name, projectId, parentEnvironmentId. Required: kind, name, projectId. 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_create: 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_create 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_create 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_create. 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_create 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