Critical Risk →

delete_env

Delete an environment variable

How to control delete_env ↓

What delete_env does on eToro MCP Server

AI agents call delete_env to permanently remove resources in eToro MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_env needs a policy

Deletion of environment variables is an irreversible operation that can break application functionality, expose configuration errors, or disable critical integrations. In a production or shared environment context (as suggested by the sibling tools involving project and deployment management), this poses a high blast radius. The destructive category takes precedence over Write because the operation cannot be undone.

From the tool's definition Tool name is 'delete_env' with description 'Delete an environment variable'. The verb 'delete' is unambiguous and irreversible—environment variables cannot be recovered once removed.

Documented attack patterns abuse exactly the kind of access delete_env gives an agent:

How to control delete_env

PolicyLayer is an MCP gateway — it sits between your AI agents and eToro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_env:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_env"
  ]
}

delete_env disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register eToro MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_env

What does the delete_env tool do? +

Delete an environment variable. It is categorised as a Destructive tool in the eToro MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_env? +

Register the eToro MCP Server MCP server in PolicyLayer and add a rule for delete_env: 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 eToro MCP Server. Nothing to install.

What risk level is delete_env? +

delete_env is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_env? +

Yes. Add a rate_limit block to the delete_env 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.

How do I block delete_env completely? +

Set action: deny in the PolicyLayer policy for delete_env. 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.

What MCP server provides delete_env? +

delete_env is provided by the eToro MCP Server MCP server (shlomico-tr/etoroportfoliomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every eToro MCP Server tool call.

Start from eToro MCP Server, 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.

154 eToro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.