the createEnvironment tool can create an environment for a given test target. an environment represents a specific setup or deployments for a test target. It include a test account when necsesary to login, a header configuration, a discovery url and a set of variables.
AI agents use createEnvironment to create or update resources in Octomind — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Octomind environment.
This tool creates new configuration data (environments) for test targets. It is reversible—environments can be modified or deleted (deleteEnvironment exists as a sibling tool). The blast radius is medium because misconfigured environments could lead to test failures, credential exposure, or testing against wrong targets, but it does not permanently destroy data, execute arbitrary code, or move funds.
From the tool's definition Tool name is 'createEnvironment' and description states it 'can create an environment' with configuration including test accounts, headers, discovery URL, and variables.
Documented attack patterns abuse exactly the kind of access createEnvironment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octomind, and nothing reaches the server without passing your rules. This is the rule we recommend for createEnvironment:
{
"version": "1",
"default": "deny",
"tools": {
"createEnvironment": {
"limits": [
{
"counter": "createenvironment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createEnvironment 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.
Free to start. No card required.
the createEnvironment tool can create an environment for a given test target. an environment represents a specific setup or deployments for a test target. It include a test account when necsesary to login, a header configuration, a discovery url and a set of variables. It is categorised as a Write tool in the Octomind MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Octomind MCP server in PolicyLayer and add a rule for createEnvironment: 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 Octomind. Nothing to install.
createEnvironment 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 createEnvironment 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 createEnvironment. 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.
createEnvironment is provided by the Octomind MCP server (octomind-dev/octomind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Octomind, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Octomind tools catalogued and risk-classified — across an index of 43,000+ MCP servers.