IP Library Granted Patent US 12,730,883
Granted Patent B1
US 12,730,883 · App. 19/530,297 · Granted Sep 8, 2026

Ephemeral nano sandbox for model context protocol server execution

Inventors: Andrew Morgan (Dublin, IE); Rahul Parwani (Atlanta, GA)
Assignee: Airia LLC
G06F21/552G06F21/53
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,730,883
App. No.
19/530,297
Granted
Sep 8, 2026
Kind
B1
Abstract

The system securely executes model context protocol (“MCP”) processes for artificial intelligence (“AI”) agents by creating nano sandboxes in which the MCP processes execute. A server-sent events (“SSE”) bridge identifies a request to initialize an SSE channel with an MCP server. The SSE bridge instantiates a nano sandbox based on a definition extracted from the request, creating a custom and dynamic isolated execution environment. An MCP process is launched within the nano sandbox. The SSE bridge returns a session identifier, receives a command and the session identifier, and forwards the command to the nano sandbox based on the session identifier. The MCP process executes the command within the nano sandbox, and responds over the SSE channel to the MCP client. When the SSE connection closes the nano sandbox can then be destroyed.

Claims (47)

1 . A method for executing model context protocol (“MCP”) processes for artificial intelligence (“AI”) agents, comprising:

receiving a hypertext transfer protocol (“HTTP”) request from an MCP client, wherein the HTTP request comprises a nano sandbox definition and a resource command for an MCP server;

instantiating, based on the nano sandbox definition, an ephemeral nano sandbox, wherein the ephemeral nano sandbox comprises an isolated execution environment;

initiating execution of the MCP server within the ephemeral nano sandbox;

transmitting the resource command to the MCP server by writing the resource command to an input interface within the ephemeral nano sandbox;

receiving a resource output from the MCP server by reading the resource output from an output interface within the ephemeral nano sandbox;

transmitting a gateway response to the MCP client, wherein the gateway response comprises the resource output; and

terminating the ephemeral nano sandbox based on transmitting the gateway response.

2 . The method of claim 1 , wherein the HTTP request is an HTTP POST, and wherein the nano sandbox definition is included in a header of the HTTP POST.

3 . The method of claim 1 , wherein the resource command is encoded in JSON-RPC format.

4 . The method of claim 1 , wherein the input interface comprises a standard input (“STDIN”) pipe of the MCP server, and wherein the output interface comprises a standard output (“STDOUT”) pipe of the MCP server.

5 . The method of claim 1 , wherein instantiating the ephemeral nano sandbox comprises executing a bubblewrap command that restricts file system access of the ephemeral nano sandbox to one or more specified directories.

6 . The method of claim 5 , wherein the bubblewrap command defines network access permissions and establishes system call filtering for the ephemeral nano sandbox.

7 . The method of claim 5 , wherein the ephemeral nano sandbox is created inside a privileged container running in Kubernetes.

8 . The method of claim 1 , wherein the ephemeral nano sandbox binds read-only system resources comprising at least one of a read-only file system, a system directory, a system library, or a system file.

9 . The method of claim 1 , wherein terminating the ephemeral nano sandbox comprises:

sending a termination signal to the MCP server;

deleting temporary files created during operation of the ephemeral nano sandbox; and

freeing memory allocations associated with the ephemeral nano sandbox.

10 . The method of claim 9 , wherein the termination signal is a SIGTERM signal, and wherein a SIGKILL signal is sent in an instance in which the MCP server does not terminate within a timeout period following the SIGTERM signal.

11 . The method of claim 1 , further comprising, prior to transmitting the resource command to the MCP server, verifying that the resource command complies with security rules.

12 . The method of claim 11 , wherein verifying that the resource command complies with security rules comprises:

checking the resource command for prompt injection; and

comparing the resource command against a whitelist of allowed commands or a blacklist of disallowed commands.

13 . The method of claim 1 , further comprising, prior to transmitting the gateway response to the MCP client, verifying that the resource output complies with security rules.

14 . The method of claim 1 , wherein a gateway receives a plurality of HTTP requests from a plurality of MCP clients, and wherein a separate ephemeral nano sandbox is instantiated for each HTTP request of the plurality of HTTP requests.

15 . The method of claim 14 , wherein each of the plurality of MCP clients are associated with different tenants, and wherein each ephemeral nano sandbox enforces tenant isolation.

16 . The method of claim 1 , wherein the MCP server is instantiated from a custom MCP package, and wherein the custom MCP package comprises at least one of a Docker container, a Node.js module, a Python module, or a GoLang binary.

17 . The method of claim 16 , wherein a deployment engine deploys the custom MCP package, and wherein the deployment engine enforces tenant isolation by preventing cross-tenant access between ephemeral nano sandboxes.

18 . The method of claim 17 , wherein the deployment engine scans the custom MCP package for malicious code prior to deployment.

19 . A non-transitory, computer-readable medium containing instructions for executing model context protocol (“MCP”) processes for artificial intelligence (“AI”) agents, wherein the instructions are executed by at least one processor to perform stages comprising:

receiving a hypertext transfer protocol (“HTTP”) request from an MCP client, wherein the HTTP request comprises a nano sandbox definition and a resource command for an MCP server;

instantiating, based on the nano sandbox definition, an ephemeral nano sandbox, wherein the ephemeral nano sandbox comprises an isolated execution environment;

initiating execution of the MCP server within the ephemeral nano sandbox;

transmitting the resource command to the MCP server by writing the resource command to an input interface within the ephemeral nano sandbox;

receiving a resource output from the MCP server by reading the resource output from an output interface within the ephemeral nano sandbox;

transmitting a gateway response to the MCP client, wherein the gateway response comprises the resource output; and

terminating the instantiation of the ephemeral nano sandbox based on transmitting the gateway response.

20 . A system for executing model context protocol (“MCP”) processes for artificial intelligence (“AI”) agents, the system comprising:

a gateway comprising at least one processor and a non-transitory memory, the gateway configured to:

receive a hypertext transfer protocol (“HTTP”) request from an MCP client, wherein the HTTP request comprises a nano sandbox definition and a resource command for an MCP server;

instantiate, based on the nano sandbox definition, an ephemeral nano sandbox, wherein the ephemeral nano sandbox comprises an isolated execution environment;

initiate execution of the MCP server within the ephemeral nano sandbox;

transmit the resource command to the MCP server by writing the resource command to an input interface within the ephemeral nano sandbox;

receive a resource output from the MCP server by reading the resource output from an output interface within the ephemeral nano sandbox;

transmit a gateway response to the MCP client, wherein the gateway response comprises the resource output; and

terminate the instantiation of the ephemeral nano sandbox based on transmitting the gateway response.

Continuity (2)
Continuation 19267456 · Jul 11, 2025
Provisional Application 63815410 · May 30, 2025
References Cited (38)
US 10192170B2 · Bates et al. · 2019 [cited by applicant]
US 10389592B2 · Lui et al. · 2019 [cited by applicant]
US 11240128B2 · Chitalia et al. · 2022 [cited by applicant]
US 11323327B1 · Chitalia et al. · 2022 [cited by applicant]
US 11392894B2 · Tatituri et al. · 2022 [cited by applicant]
US 11508371B2 · Kothari et al. · 2022 [cited by applicant]
US 11922220B2 · Haghighat et al. · 2024 [cited by applicant]
US 11977471B2 · Casati et al. · 2024 [cited by applicant]
US 12021693B1 · Chitalia et al. · 2024 [cited by applicant]
US 12141726B2 · Cook · 2024 [cited by applicant]
US 12242521B2 · Zarokian et al. · 2025 [cited by applicant]
US 12282557B2 · Shear et al. · 2025 [cited by applicant]
US 12393676B1 · Morgan · 2025 [cited by applicant]
US 12541517B2 · Schieferstein et al. · 2026 [cited by applicant]
US 12541797B2 · Kloeppel et al. · 2026 [cited by applicant]
US 12549574B1 · Morgan et al. · 2026 [cited by applicant]
US 12561683B2 · Bansal et al. · 2026 [cited by applicant]
US 12562968B1 · Morgan et al. · 2026 [cited by applicant]
US 12568091B1 · Morgan et al. · 2026 [cited by applicant]
US 12574336B1 · Morgan et al. · 2026 [cited by applicant]
US 20190294779A1 · Suneja · 2019 [cited by applicant]
US 20220027178A1 · Caldarale · 2022 [cited by applicant]
US 20250005836A1 · Chu · 2025 [cited by applicant]
US 20250139446A1 · Li et al. · 2025 [cited by applicant]
US 20250156828A1 · Sliwka · 2025 [cited by applicant]
US 20250190966A1 · Gutierrez-Sheris · 2025 [cited by applicant]
US 20250244970A1 · Sundaram · 2025 [cited by applicant]
US 20250292250A1 · Makeig · 2025 [cited by applicant]
US 20250371225A1 · Lesnik · 2025 [cited by examiner]
US 20250390352A1 · Crabtree · 2025 [cited by examiner]
US 20260010623A1 · Kerkar et al. · 2026 [cited by applicant]
US 20260058997A1 · Qureshi · 2026 [cited by applicant]
CN 120029517A · 2025 [cited by applicant]
CN 120547240A · 2025 [cited by applicant]
CN 120560800A · 2025 [cited by applicant]
Ivo Brett, Simplified and Secure MCP Gateways for Enterprise AI Integration, 2025, CISSP, B .Eng, MSc Solution Architect/Educator independent.academia.edu/ivobrett, pp. 1-4 (Year: 2025). [cited by applicant]
Wen et al; From stdio to HTTP SSE: Host Your MCP Server with APISIX API Gateway; Apr. 21, 2025; The Apache Software Foundation; pp. 1-10. (Year: 2025). [cited by applicant]
Olawade, David B., et al. “The synergy of artificial intelligence and nanotechnology towards advancing innovation and sustainability—A mini-review.” Nano Trends 8 (2024): 100052. [cited by applicant]