# check_connection

Пошагово проверяет подключение: сервер-посредник (если указан), публикацию OData, логин и пароль 1С, состав объектов. Вызывай, когда пользователь просит проверить связь, и при любой ошибке подключения.

Agent View of the PolicyLayer registry record for `check_connection`. HTML page: https://policylayer.com/tools/1c-claude-connector/check-connection

## Facts

- Tool: `check_connection`
- Server: 1c Claude Connector (`glxaoc/1c-claude-connector`) — https://policylayer.com/tools/1c-claude-connector.md
- Homepage: https://github.com/glxaoc/1c-claude-connector
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- 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": "check_connection",
    "arguments": {}
  }
}
```

## Why check_connection is rated Low

Diagnostic tool that verifies credentials and connectivity without modifying or executing actions on 1C data.

From the tool's own definition: "checks connection, authentication, server status, object composition"

## Use case

AI agents call check_connection to retrieve information from 1c Claude Connector 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 1c Claude Connector:

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

## Other tools on 1c Claude Connector (4)

- `count` — Read — https://policylayer.com/tools/1c-claude-connector/count.md
- `describe_object` — Read — https://policylayer.com/tools/1c-claude-connector/describe-object.md
- `list_objects` — Read — https://policylayer.com/tools/1c-claude-connector/list-objects.md
- `query` — Read — https://policylayer.com/tools/1c-claude-connector/query.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=1c-claude-connector · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1c-claude-connector
