coding_session_restart
Restart the coding CLI session on the selected runner node. Use when the CLI is stuck or erroring.
This record as markdown: /tools/io-github-proagentstore-platform/coding-session-restart.md
What coding_session_restart does on ProAgentStore
AI agents invoke coding_session_restart to trigger actions in ProAgentStore. 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.
Why coding_session_restart is rated High
Restarts a CLI session on a runner node, triggering external operations with unpredictable side effects on infrastructure.
From the tool's definition Restart the coding CLI session on the selected runner node.
Attacks that exploit this kind of access
The rule that runs coding_session_restart safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coding_session_restart, this is the rule to start with:
coding_session_restart 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.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every coding_session_restart call is checked against it from then on.
Questions about coding_session_restart
Restart the coding CLI session on the selected runner node. Use when the CLI is stuck or erroring. It is categorised as a Execute tool in the ProAgentStore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for coding_session_restart: 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 ProAgentStore. Nothing to install.
coding_session_restart 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 coding_session_restart 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 coding_session_restart. 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.
coding_session_restart is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue