Low Risk

roamzy_get_esim

Get a specific eSIM by id, including msisdn, status, balance, and the activation block (qr_payload + lpa_url). ⚠️ QR RENDERING: This tool does NOT return a ready-to-display image. Instead, qr_payload contains the LPA URI string. YOU must generate the QR PNG yourself using your code-execution tool...

Part of the Mcp Server server.

roamzy_get_esim is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MCP SERVER →

Free to start. No card required.

AI agents call roamzy_get_esim to retrieve information from Mcp Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though roamzy_get_esim only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "roamzy_get_esim": {}
  }
}

See the full Mcp Server policy for all 12 tools.

Get this rule live on your own Mcp Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP SERVER →

View all 12 tools →

These attack patterns abuse exactly the kind of access roamzy_get_esim gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so roamzy_get_esim only ever does what you allow.

SECURE MCP SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the roamzy_get_esim tool do? +

Get a specific eSIM by id, including msisdn, status, balance, and the activation block (qr_payload + lpa_url). ⚠️ QR RENDERING: This tool does NOT return a ready-to-display image. Instead, qr_payload contains the LPA URI string. YOU must generate the QR PNG yourself using your code-execution tools (Python qrcode library, JS qrcode npm package, etc.) and offer the resulting PNG as a downloadable file to the user. DO NOT use external QR-generation services — they show ugly UI dialogs in Claude Desktop and require external trust. Local generation gives the user a real downloadable PNG they can save and scan. ALWAYS caption the QR (once generated) with «Your eSIM number: <msisdn>». The lpa_url field is ONLY for users installing on the SAME phone where they're reading the chat (camera can't scan own screen) — surface it as a text fallback for that case, prefixed «LPA URI (manual entry):». Do NOT show internal IDs (id, display_id, iccid) to the user. ⚠️ ANON-MODE RECOVERY REMINDER: If this is an anonymous Roamzy session (no ROAMZY_API_TOKEN env was set), after presenting the QR you MUST also re-surface the claim_url from the original roamzy_create_order response with this framing: «❗ Be sure to save this recovery link — without it you will not be able to get back to this eSIM from a different Claude chat». If the user has already closed-and-reopened the chat and lost the claim_url, instruct them to contact Roamzy support (call roamzy_support tool) with their MSISDN + NowPayments transaction hash for manual recovery — operator can mint a fresh claim_url. If the user follows up with «how do I contact support» or «refund» — call roamzy_support, not web search.. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on roamzy_get_esim? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for roamzy_get_esim: 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 Mcp Server. Nothing to install.

What risk level is roamzy_get_esim? +

roamzy_get_esim is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit roamzy_get_esim? +

Yes. Add a rate_limit block to the roamzy_get_esim 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.

How do I block roamzy_get_esim completely? +

Set action: deny in the PolicyLayer policy for roamzy_get_esim. 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.

What MCP server provides roamzy_get_esim? +

roamzy_get_esim is provided by the Mcp Server MCP server (@roamzy/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Server tool call.

Deterministic rules across all 12 Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.