Create and initialize OSS environment variables with the specified endpoint, access key ID, access key secret, security token, and region.
AI agents use oss_env_init to create or update resources in Wuying AgentBay — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wuying AgentBay environment.
This tool performs reversible modification of system state (environment variables) rather than permanent deletion. While it handles sensitive credentials (access keys, security tokens), the action itself is Write-class—environment variables can be modified or cleared.
From the tool's definition The tool description states it will 'Create and initialize OSS environment variables with the specified endpoint, access key ID, access key secret, security token, and region.' This involves creating/modifying configuration state by setting environment…
Documented attack patterns abuse exactly the kind of access oss_env_init gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wuying AgentBay, and nothing reaches the server without passing your rules. This is the rule we recommend for oss_env_init:
{
"version": "1",
"default": "deny",
"tools": {
"oss_env_init": {
"limits": [
{
"counter": "oss_env_init_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}oss_env_init 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.
Create and initialize OSS environment variables with the specified endpoint, access key ID, access key secret, security token, and region. It is categorised as a Write tool in the Wuying AgentBay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wuying AgentBay MCP server in PolicyLayer and add a rule for oss_env_init: 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 Wuying AgentBay. Nothing to install.
oss_env_init 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 oss_env_init 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 oss_env_init. 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.
oss_env_init is provided by the Wuying AgentBay MCP server (michael98671/agentbay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wuying AgentBay, 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.
59 Wuying AgentBay tools catalogued and risk-classified — across an index of 43,000+ MCP servers.