AI agents invoke sandy_resume_session to trigger actions in Sandy. 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.
This tool resumes an execution session within a sandboxed TypeScript/AWS SDK environment. Resuming a session reactivates an execution context that can run code against AWS accounts, making it Execute-category. Severity is medium because the session itself is sandboxed, but resuming it could enable subsequent code execution with cross-account AWS access.
From the tool's definition 'Resume an existing session' — reactivates a previously created execution session in a sandboxed code-execution environment; 'return its scripts path' indicates it restores an active execution context
Attacks that exploit this kind of access
Resume an existing session and return its scripts path. It is categorised as a Execute tool in the Sandy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sandy MCP server in PolicyLayer and add a rule for sandy_resume_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 Sandy. Nothing to install.
sandy_resume_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 sandy_resume_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 sandy_resume_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.
sandy_resume_session is provided by the Sandy MCP server (jamestelfer/sandy). 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 →