Start a guarded paid EC2+SSM smoke run and terminate the instance after completion.
AI agents invoke start_ec2_smoke_run to trigger actions in AWS Notebook Runner MCP. 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 executes code (Jupyter notebooks) on remote cloud infrastructure, which is inherently Execute-category behavior. While it includes safeguards ('guarded', 'dry-run planning' available via sibling tools, 'automatic cleanup'), the core action is triggering external computation whose effects depend on notebook contents.
From the tool's definition Starts a paid EC2 instance ('Start a guarded paid EC2+SSM smoke run'), executes notebook code on it via SSM (Systems Manager), and terminates the instance ('terminate the instance after completion').
Attacks that exploit this kind of access
Start a guarded paid EC2+SSM smoke run and terminate the instance after completion. It is categorised as a Execute tool in the AWS Notebook Runner MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Notebook Runner MCP server in PolicyLayer and add a rule for start_ec2_smoke_run: 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 AWS Notebook Runner MCP. Nothing to install.
start_ec2_smoke_run 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 start_ec2_smoke_run 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 start_ec2_smoke_run. 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.
start_ec2_smoke_run is provided by the AWS Notebook Runner MCP server (yummytastycode/aws-notebook-runner-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 →