check_connection
Пошагово проверяет подключение: сервер-посредник (если указан), публикацию OData, логин и пароль 1С, состав объектов. Вызывай, когда пользователь просит проверить связь, и при любой ошибке подключения.
This record as markdown: /tools/1c-claude-connector/check-connection.md
What check_connection does on 1c Claude Connector
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.
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 definition checks connection, authentication, server status, object composition
Attacks that exploit this kind of access
The rule that runs check_connection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1c Claude Connector, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_connection, this is the rule to start with:
check_connection 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 1c Claude Connector, apply this rule, and every check_connection call is checked against it from then on.
Questions about check_connection
Пошагово проверяет подключение: сервер-посредник (если указан), публикацию OData, логин и пароль 1С, состав объектов. Вызывай, когда пользователь просит проверить связь, и при любой ошибке подключения. It is categorised as a Read tool in the 1c Claude Connector MCP Server, which means it retrieves data without modifying state.
Register the 1c Claude Connector MCP server in PolicyLayer and add a rule for check_connection: 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 1c Claude Connector. Nothing to install.
check_connection 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_connection 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_connection. 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_connection is provided by the 1c Claude Connector MCP server (glxaoc/1c-claude-connector). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1c Claude Connector, and thousands of servers like it.
This server
Across the catalogue