AI agents use update_secret_name to create or update resources in eToro MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your eToro MCP Server environment.
This tool modifies metadata of a secret (its name) but does not create, delete, or expose the secret itself. The change is reversible—the name can be changed again. While the sibling tools suggest this server may manage infrastructure/authentication secrets, renaming a secret is a reversible write operation.
From the tool's definition Tool name 'update_secret_name' and description 'Change the name of a secret' indicate a modification operation. The verb 'Change' and 'update' are characteristic of Write-class operations that alter existing data reversibly.
Documented attack patterns abuse exactly the kind of access update_secret_name 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 update_secret_name:
{
"version": "1",
"default": "deny",
"tools": {
"update_secret_name": {
"limits": [
{
"counter": "update_secret_name_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_secret_name stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Change the name of a secret. It is categorised as a Write tool in the eToro MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the eToro MCP Server MCP server in PolicyLayer and add a rule for update_secret_name: 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.
update_secret_name is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_secret_name 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 update_secret_name. 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.
update_secret_name 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.