Retrieves all Aliases for the Deployment with the given ID
AI agents call list_deployment_aliases 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 is a straightforward data retrieval operation. It fetches and lists aliases associated with a specific deployment ID. There are no side effects, no data modification, no code execution, no deletion, and no financial implications. This is a simple query operation consistent with the Read category.
From the tool's definition The tool name 'list_deployment_aliases' and description 'Retrieves all Aliases for the Deployment with the given ID' indicate a read-only operation that queries and returns existing deployment alias data without modifying state.
Documented attack patterns abuse exactly the kind of access list_deployment_aliases 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 list_deployment_aliases:
{
"version": "1",
"default": "deny",
"tools": {
"list_deployment_aliases": {}
}
} list_deployment_aliases 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.
Retrieves all Aliases for the Deployment with the given ID. 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 list_deployment_aliases: 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.
list_deployment_aliases 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 list_deployment_aliases 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 list_deployment_aliases. 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.
list_deployment_aliases 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.