# get_business_context

Get Gitsim product knowledge, pricing model, IP routing guidance, and eSIM fundamentals. Call this FIRST before helping a customer so you understand the product.

Agent View of the PolicyLayer registry record for `get_business_context`. HTML page: https://policylayer.com/tools/com-gitsim-chat/get-business-context

## Facts

- Tool: `get_business_context`
- Server: Gitsim Chat (`https://chat.gitsim.com/api/mcp`) — https://policylayer.com/tools/com-gitsim-chat.md
- Homepage: https://github.com/https://chat.gitsim.com/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_business_context",
    "arguments": {}
  }
}
```

## Why get_business_context is rated Low

This tool performs read-only operations to fetch informational content about Gitsim's products, pricing, and technical guidance. It has no capability to create, modify, delete, or execute external operations. The low severity reflects minimal blast radius—misuse would yield incorrect information to a customer at worst, not data loss, financial exposure, or system compromise.

From the tool's own definition: "Tool retrieves product knowledge, pricing model, and eSIM fundamentals without modifying any data. The description indicates 'Get' (retrieval) operations only, with no side effects or state changes."

## Use case

AI agents call get_business_context 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Gitsim Chat:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_business_context": {}
  }
}
```

## Other tools on Gitsim Chat (8)

- `buy_topup` — Financial — https://policylayer.com/tools/com-gitsim-chat/buy-topup.md
- `create_order` — Financial — https://policylayer.com/tools/com-gitsim-chat/create-order.md
- `check_data_balance` — Read — https://policylayer.com/tools/com-gitsim-chat/check-data-balance.md
- `check_order_status` — Read — https://policylayer.com/tools/com-gitsim-chat/check-order-status.md
- `get_package` — Read — https://policylayer.com/tools/com-gitsim-chat/get-package.md
- `list_esims` — Read — https://policylayer.com/tools/com-gitsim-chat/list-esims.md
- `search_packages` — Read — https://policylayer.com/tools/com-gitsim-chat/search-packages.md
- `search_topup_packages` — Read — https://policylayer.com/tools/com-gitsim-chat/search-topup-packages.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gitsim-chat · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gitsim-chat