make_permanent
Promote an existing (ephemeral) sandbox to an always-on machine: keeps the SAME sandboxId, disarms the host reaper, and starts flat MXN/month billing for the chosen tier. The
This record as markdown: /tools/cloud-easybits-easybits/make-permanent.md
What make_permanent does on EasyBits
AI agents use make_permanent to commit financial operations through EasyBits, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why make_permanent is rated Critical
Tool commits to recurring monthly financial billing obligations automatically.
From the tool's definition starts flat MXN/month billing for the chosen tier
Attacks that exploit this kind of access
The rule that runs make_permanent 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 make_permanent, this is the rule to start with:
Any call to make_permanent is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every make_permanent call is checked against it from then on.
Questions about make_permanent
Promote an existing (ephemeral) sandbox to an always-on machine: keeps the SAME sandboxId, disarms the host reaper, and starts flat MXN/month billing for the chosen tier. The. It is categorised as a Financial tool in the EasyBits MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the EasyBits MCP server in PolicyLayer and add a rule for make_permanent: 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.
make_permanent is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the make_permanent 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 make_permanent. 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.
make_permanent 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.
Across the catalogue