list_esims

List the customer's delivered eSIMs. Requires a session key from a previous tool call.

SERVERGitsim Chat SOURCEhttps://chat.gitsim.com/api/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-gitsim-chat/list-esims.md

WHAT IT DOES

What list_esims does on Gitsim Chat

AI agents call list_esims to retrieve information from Gitsim Chat without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`session_key`	string	Yes	Session key from a previous tool call

Parameters from the server's own tool schema.

RISK

Why list_esims is rated Low

This tool retrieves existing eSIM records for a customer. It performs a simple query/read operation to display data without creating, modifying, deleting, or executing any operations. The requirement for a session key is a security control that does not change the read-only nature of the operation.

From the tool's definition Tool description states it 'List the customer's delivered eSIMs' and 'Requires a session key from a previous tool call.' The verb 'list' indicates a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_esims safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitsim Chat, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_esims, this is the rule to start with:

list_esims Allowed

list_esims is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_esims": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitsim Chat, apply this rule, and every list_esims call is checked against it from then on.

FAQ

Questions about list_esims

What does the list_esims tool do? +

List the customer's delivered eSIMs. Requires a session key from a previous tool call. It is categorised as a Read tool in the Gitsim Chat MCP Server, which means it retrieves data without modifying state.

What parameters does list_esims accept? +

list_esims accepts 1 parameter: session_key. Required: session_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_esims? +

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

What risk level is list_esims? +

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

Can I rate-limit list_esims? +

Yes. Add a rate_limit block to the list_esims 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 list_esims completely? +

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

list_esims is provided by the Gitsim Chat MCP server (https://chat.gitsim.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitsim Chat, and thousands of servers like it.

This server

All 9 Gitsim Chat tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →