Close the current 1C session — the session that executes 1C tool calls — and return a launcher script command to start a new one. Use when exclusive database access is needed (e.g. updating configuration). Run the returned command synchronously: exit 0 means the session is ready. On Windows, run ...
AI agents use close_1c_session to create or update resources in 1C MCP Toolkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1C MCP Toolkit environment.
An AI agent can call close_1c_session faster than any human can review — one bad instruction and it creates or modifies resources in 1C MCP Toolkit by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access close_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 close_1c_session:
{
"version": "1",
"default": "deny",
"tools": {
"close_1c_session": {
"limits": [
{
"counter": "close_1c_session_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}close_1c_session stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Close the current 1C session — the session that executes 1C tool calls — and return a launcher script command to start a new one. Use when exclusive database access is needed (e.g. updating configuration). Run the returned command synchronously: exit 0 means the session is ready. On Windows, run the command in PowerShell (not cmd.exe). On timeout, check whether a 1C process was started before launching another. On non-timeout exit 1, read the output: pre-launch errors are safe to retry after fixing the cause; failed startup errors close the failed new instance automatically. NOTE: on Linux with password auth, python3 must be available on PATH. IMPORTANT: Do NOT call this on your own initiative. It is categorised as a Write tool in the 1C MCP Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 1C MCP Toolkit MCP server in PolicyLayer and add a rule for close_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.
close_1c_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_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 close_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.
close_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.