Run build, test, and lint sequentially for a project. Auto-detects platform-specific commands. Side effects: executes up to 3 shell commands with 5-minute timeouts each. Returns per-gate results and an overall pass/fail status. Use this as a quality gate before committing or ending a session. Use...
AI agents invoke verify_all to trigger actions in Claude Session Continuity. 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.
The tool explicitly runs shell commands (build, test, lint) on the host system. Executing arbitrary shell commands with 5-minute timeouts per command represents a significant execution surface. While the described use case is benign quality-gating, the mechanism is shell execution, which could have wide blast radius if misused or if the auto-detected commands are manipulated.
From the tool's definition 'executes up to 3 shell commands with 5-minute timeouts each' and 'Run build, test, and lint sequentially'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Run build, test, and lint sequentially for a project. Auto-detects platform-specific commands. Side effects: executes up to 3 shell commands with 5-minute timeouts each. Returns per-gate results and an overall pass/fail status. Use this as a quality gate before committing or ending a session. Use verify_build or verify_test individually when you only need one check. It is categorised as a Execute tool in the Claude Session Continuity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for verify_all: 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 Claude Session Continuity. Nothing to install.
verify_all 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 verify_all 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 verify_all. 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.
verify_all is provided by the Claude Session Continuity MCP server (leesgit/claude-session-continuity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →