Restart the current 1C session — the session that executes 1C tool calls. A restart is typically required after updating the 1C configuration (metadata, extensions, BSL code) so the new session picks up the changes. The new session starts automatically with the same database and connection settin...
AI agents invoke restart_1c_session to trigger actions in 1C MCP Toolkit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Although superficially administrative, restarting a session is an Execute-category action: it triggers an external operation (session termination and reinitiation) with irreversible intermediate effects (current session destruction, potential loss of unsaved work).
From the tool's definition Tool performs 'Restart the current 1C session' — an action that terminates and reinitializes a live system process with side effects (session shutdown, automatic reconnection with preserved state).
Documented attack patterns abuse exactly the kind of access restart_1c_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 1C MCP Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for restart_1c_session:
{
"version": "1",
"default": "deny",
"tools": {
"restart_1c_session": {
"limits": [
{
"counter": "restart_1c_session_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}restart_1c_session stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Restart the current 1C session — the session that executes 1C tool calls. A restart is typically required after updating the 1C configuration (metadata, extensions, BSL code) so the new session picks up the changes. The new session starts automatically with the same database and connection settings; anonymization state is preserved. The current session shuts down once the new one is ready. IMPORTANT: Do NOT call this tool on your own initiative. Only invoke it when explicitly instructed — either by the user directly or as a defined step in a pipeline or task specification. Never infer that a restart is needed and call it autonomously. It is categorised as a Execute tool in the 1C MCP Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1C MCP Toolkit MCP server in PolicyLayer and add a rule for restart_1c_session: 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 MCP Toolkit. Nothing to install.
restart_1c_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the restart_1c_session 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 restart_1c_session. 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.
restart_1c_session is provided by the 1C MCP Toolkit MCP server (roctup/1c-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 1C MCP Toolkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 1C MCP Toolkit tools catalogued and risk-classified — across an index of 42,500+ MCP servers.