check_data_balance
Check remaining data balance on an eSIM. Requires a session key and the eSIM's ICCID.
This record as markdown: /tools/com-gitsim-chat/check-data-balance.md
What check_data_balance does on Gitsim Chat
AI agents call check_data_balance 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 |
|---|---|---|---|
iccid | string | Yes | The ICCID of the eSIM to check |
session_key | string | Yes | Session key from a previous tool call |
Parameters from the server's own tool schema.
Why check_data_balance is rated Low
This tool retrieves the current data balance of an eSIM without modifying any data. It is a read-only query operation. The low severity reflects that exposure only reveals usage information on a specific eSIM, with blast radius limited to data disclosure of the queried service.
From the tool's definition Tool name 'check_data_balance' and description 'Check remaining data balance' indicate a query operation with no side effects. Requires authentication (session key) and identifier (ICCID) but only retrieves information.
Attacks that exploit this kind of access
The rule that runs check_data_balance 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 check_data_balance, this is the rule to start with:
check_data_balance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitsim Chat, apply this rule, and every check_data_balance call is checked against it from then on.
Questions about check_data_balance
Check remaining data balance on an eSIM. Requires a session key and the eSIM's ICCID. It is categorised as a Read tool in the Gitsim Chat MCP Server, which means it retrieves data without modifying state.
check_data_balance accepts 2 parameters: iccid, session_key. Required: iccid, session_key. The full parameter table on this page comes from the server's own tool schema.
Register the Gitsim Chat MCP server in PolicyLayer and add a rule for check_data_balance: 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.
check_data_balance is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_data_balance 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 check_data_balance. 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.
check_data_balance 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.
More on Gitsim Chat, and thousands of servers like it.
This server
Across the catalogue