AI agents call get_env to retrieve information from eToro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves environment variables, which is a read-only operation that queries system configuration. It has no destructive, financial, or code-execution implications. The severity is low because environment variable exposure depends on what sensitive data might be stored in them, but the tool itself only performs lookup.
From the tool's definition Tool name 'get_env' and description 'Get an environment variable' indicate retrieval of configuration data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_env gives an agent:
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 get_env:
{
"version": "1",
"default": "deny",
"tools": {
"get_env": {}
}
} get_env is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get an environment variable. It is categorised as a Read tool in the eToro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the eToro MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_env is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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.