AI agents use issue_cert 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.
Issuing a certificate creates a new credential artifact that modifies the system state reversibly (certificates can be revoked/reissued). This is a Write operation rather than Execute because it doesn't run arbitrary code—it creates a specific resource type. Severity is medium because certificate issuance could enable unauthorized access if misused, but impact depends on the certificate scope and permissions.
From the tool's definition Tool name 'issue_cert' and description 'Issue a new certificate' indicate creation of a digital certificate, which is a write operation that creates new data/credentials.
Documented attack patterns abuse exactly the kind of access issue_cert 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 issue_cert:
{
"version": "1",
"default": "deny",
"tools": {
"issue_cert": {
"limits": [
{
"counter": "issue_cert_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}issue_cert 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.
Issue a new certificate. 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 issue_cert: 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.
issue_cert 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 issue_cert 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 issue_cert. 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.
issue_cert 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.