Create a new deployment with all required data
AI agents invoke create_deployment to trigger actions in eToro MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Creating a deployment runs an external operation that provisions or launches services. This is an Execute-category action since it triggers infrastructure changes. Confidence is moderate because the server description mentions eToro public API tools (portfolios, instruments), yet the sibling tools (cancel_deployment, add_domain, create_auth_token) suggest this is a deployment/hosting platform context.
From the tool's definition 'Create a new deployment with all required data' — deploying new code/infrastructure triggers external operations
Documented attack patterns abuse exactly the kind of access create_deployment 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 create_deployment:
{
"version": "1",
"default": "deny",
"tools": {
"create_deployment": {
"limits": [
{
"counter": "create_deployment_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_deployment stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new deployment with all required data. It is categorised as a Execute tool in the eToro MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the eToro MCP Server MCP server in PolicyLayer and add a rule for create_deployment: 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.
create_deployment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_deployment 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 create_deployment. 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.
create_deployment 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.