coding_session_fresh
End the current session and start a brand new one (clean state, no --resume). Fixes corrupted CLI state.
This record as markdown: /tools/io-github-proagentstore-platform/coding-session-fresh.md
What coding_session_fresh does on ProAgentStore
AI agents invoke coding_session_fresh 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_fresh is rated High
This tool executes a session reset operation whose effects depend on the current state and intended outcome. While not destructive in the sense of permanent data loss, it terminates a running session (a significant operational state change) and reinitializes it. This is execution of an external operation (CLI session management) rather than a simple data read or write.
From the tool's definition Tool description states it will 'End the current session and start a brand new one' and 'Fixes corrupted CLI state' — these are active operations that trigger external state changes in a CLI environment.
Attacks that exploit this kind of access
The rule that runs coding_session_fresh 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_fresh, this is the rule to start with:
coding_session_fresh 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_fresh call is checked against it from then on.
Questions about coding_session_fresh
End the current session and start a brand new one (clean state, no --resume). Fixes corrupted CLI state. 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_fresh: 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_fresh 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_fresh 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_fresh. 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_fresh 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