Creates a new environment in a project
AI agents use create_environment to create or update resources in Keyshade — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keyshade environment.
Creating an environment in a secrets management platform modifies the project structure reversibly. This is a Write operation (not Execute, as it doesn't run code or trigger external operations; not Destructive, as it is reversible and doesn't delete data; not Financial).
From the tool's definition Tool name is 'create_environment' and description states 'Creates a new environment in a project' — this is a create operation that adds a new resource to the system.
Documented attack patterns abuse exactly the kind of access create_environment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Keyshade, and nothing reaches the server without passing your rules. This is the rule we recommend for create_environment:
{
"version": "1",
"default": "deny",
"tools": {
"create_environment": {
"limits": [
{
"counter": "create_environment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_environment 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.
Creates a new environment in a project. It is categorised as a Write tool in the Keyshade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keyshade 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 Keyshade. 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 Keyshade MCP server (keyshade-xyz/keyshade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Keyshade, 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.
44 Keyshade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.