Create an environment in a project.
AI agents use create_environment to create or update resources in Infisical MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Infisical MCP environment.
This tool creates a new environment, which is a reversible operation. Environments are organizational structures used to manage secrets and configurations (dev, staging, prod, etc.). While creating an environment can have operational impact (e.g., enabling secret management in a new environment), the operation is not destructive and does not move money or execute arbitrary code. It is reversible by deletion.
From the tool's definition Tool name 'create_environment' and description 'Create an environment in a project' indicate creation of new configuration data within Infisical.
Attacks that exploit this kind of access
Create an environment in a project. It is categorised as a Write tool in the Infisical MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Infisical MCP server in PolicyLayer and add a rule for create_environment: 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 Infisical MCP. Nothing to install.
create_environment 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 create_environment 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 create_environment. 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.
create_environment is provided by the Infisical MCP server (plgonzalezrx8/infisicalmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →