unset_machine_secret
Stop injecting an env var into this machine. Restarts the app right away, so it loses the var NOW — if it needs it to boot, it will not come up. The value stays in the account vault, so it can be wired back with set_machine_secrets.
This record as markdown: /tools/cloud-easybits-easybits/unset-machine-secret.md
What unset_machine_secret does on EasyBits
AI agents use unset_machine_secret to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why unset_machine_secret is rated Medium
Modifies machine configuration reversibly by removing environment variables; restart ensures immediate effect but change is undoable via set_machine_secrets.
From the tool's definition Stop injecting env var, restarts app, loses var NOW
Attacks that exploit this kind of access
The rule that runs unset_machine_secret safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unset_machine_secret, this is the rule to start with:
unset_machine_secret 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 EasyBits, apply this rule, and every unset_machine_secret call is checked against it from then on.
Questions about unset_machine_secret
Stop injecting an env var into this machine. Restarts the app right away, so it loses the var NOW — if it needs it to boot, it will not come up. The value stays in the account vault, so it can be wired back with set_machine_secrets. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for unset_machine_secret: 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 EasyBits. Nothing to install.
unset_machine_secret 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 unset_machine_secret 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 unset_machine_secret. 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.
unset_machine_secret is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue