start_ec2_smoke_run_async

Start a guarded paid EC2+SSM smoke run and return immediately with run ids.

Server AWS Notebook Runner MCP yummytastycode/aws-notebook-runner-mcp
Category Execute
Risk class High
Parameters 00 required

What start_ec2_smoke_run_async does on AWS Notebook Runner MCP

AI agents invoke start_ec2_smoke_run_async 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.

Why start_ec2_smoke_run_async needs a policy

This tool executes arbitrary notebook code on AWS EC2 instances, which is a form of Execute: it runs code whose effects depend on notebook contents and incurs financial costs (marked 'paid'). While Financial considerations exist (cost implications), the primary capability is code execution on remote infrastructure.

From the tool's definition Tool description states 'Start a guarded paid EC2+SSM smoke run' — actively launches cloud compute infrastructure.

Questions about start_ec2_smoke_run_async

What does the start_ec2_smoke_run_async tool do? +

Start a guarded paid EC2+SSM smoke run and return immediately with run ids. 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.

How do I enforce a policy on start_ec2_smoke_run_async? +

Register the AWS Notebook Runner MCP server in PolicyLayer and add a rule for start_ec2_smoke_run_async: 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.

What risk level is start_ec2_smoke_run_async? +

start_ec2_smoke_run_async is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_ec2_smoke_run_async? +

Yes. Add a rate_limit block to the start_ec2_smoke_run_async 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.

How do I block start_ec2_smoke_run_async completely? +

Set action: deny in the PolicyLayer policy for start_ec2_smoke_run_async. 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.

What MCP server provides start_ec2_smoke_run_async? +

start_ec2_smoke_run_async 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.