DataRobot MLOps can register GenAI apps running on external environments as external model deployments. This allows for both monitoring of prediction activities and optionally enforcing guardrails
by attaching a “guard” to these entrypoints.

guard and aguard are Python decorators that accelerate enhancing an existing app with these capabilities for development and testing purposes.


Using these decorators on mission-critical production apps is not advised. Some limitations include:

  • Risks of being unable to report all predictions to DR ML Ops during spikes of heavy usage due to REST rate-limiting

  • Unintended interactions between threaded application code and the threads used by guard to report data to ML Ops concurrently

For production use we recommend installing and integrating the official ML Ops tracking agent into your production code and environment.

Potential use cases#

Using DataRobot MLOps, you can track your external LLM app’s service health. This includes monitoring request counts, response times and other possible custom metrics of interest.

Use of guard or aguard also allow you to alter your app’s responses based on specific rules, such as allowing prompts within preferred topics or intercepting the completion process if the content has undesired attributes, such as toxicity, high probability for prompt injection/jailbreak or is irrelevant to the prompt, etc.

In order to set up such a system with monitoring and guardrails in place, it’s necessary to evaluate the app’s inputs (prompts) using a secondary (e.g. sidecar) model. If the secondary model flags the inputs, a preset response informs the user, and the event is recorded. This data, including prompt and completion details, is then logged on DataRobot MLOps for monitoring and/or future analysis.

Guardrail examples#


To add a guard to your app, DataRobot deployments for both the LLM app and the optional guard model are needed. This guard model deployment contains the decision-making logic to determine if the provided input meets the acceptable use criteria. Based on its decision logic, it labels the input as flagged or unflagged and conveys this information back to its invoker, i.e., the DRX guard decorator.

Both guard and aguard can be used without a guardrail to easily attach stand-alone monitoring to an external app.

Registering an LLM application as an External Deployment in DataRobot#

from datarobot.mlops.connected.client import MLOpsClient
from datarobotx.common.config import context

service_url = context.endpoint.split("/api")[0]
mlops_client = MLOpsClient(service_url=service_url, api_key=context.token, verify=True)

pred_env = {
    "name": "External Prediction Environment",
    "description": "Prediction environment for external LLM apps using DR Guardrails - created via drx",
    "platform": "other",
    "supportedModelFormats": ["externalModel"],
pred_env_id = mlops_client.create_prediction_environment(pred_env)

model_pkg_name = "External LLM app"
model_pkg = {
    "name": model_pkg_name,
    "modelDescription": {
        "modelName": model_pkg_name,
        "description": f"{model_pkg_name} - created via drx",
    "target": {"type": "Regression", "name": "dummy_reg_val"},
model_pkg_id = mlops_client.create_model_package(model_pkg)

ext_depl_id = mlops_client.deploy_model_package(
    f"{model_pkg_name} Deployment",
mlops_client.update_deployment_settings(ext_depl_id, target_drift=True, feature_drift=True)
model_id = mlops_client.get_deployment(ext_depl_id)["model"]["id"]

These steps can also be easily performed from the DataRobot GUI.

Deploying a guardrail model as a Custom Unstructured Model#

Here’s how you can create a toxicity guardrail as an Unstructured Custom Model Deployment in DataRobot MLOps, using drx.deploy()

from datarobotx import deploy
from transformers import pipeline

pipe = pipeline(
MODEL_NAME = "toxic-bert"
path = f"./{MODEL_NAME}"

def load_model(input_dir):
    from transformers import (  # pylint: disable=reimported

    model_path = input_dir + "/" + MODEL_NAME
    model = AutoModelForSequenceClassification.from_pretrained(model_path)
    tokenizer = AutoTokenizer.from_pretrained(model_path)
    return pipeline(

def score_unstructured(model, data, query, **kwargs):
    import json

    data_dict = json.loads(data)
    outputs = model(data_dict["prompt"])
    rv = {"flagged": outputs[0]["score"] > 0.5}
    return json.dumps(rv)

guard = deploy(
        hooks={"load_model": load_model, "score_unstructured": score_unstructured},
        environment_id='64c964448dd3f0c07f47d040', # DR GenAI drop-in environment

Configuring the DRX guard decorator#

from datarobotx.llm.chains.guard import aguard, MonitoringConfig, GuardrailConfig

monitor_config = MonitoringConfig(
    inputs_parser=lambda x: {"prompt": x}

guardrail_config = GuardrailConfig(,
    input_parser=lambda x: {"prompt": x},
@aguard(monitor_config, guardrail_config)
async def llm_proxy(prompt):
    #Here's where you call out to an LLM model and get completions for the input prompt
    completion = call_llm(prompt)
    return completion

Now that the setup is done, let’s test our guarded LLM application.

First, let’s call the llm_proxy function as usual, with a prompt that is not toxic. The response of this function call should be the same as the unguarded LLM app’s completion to the same prompt, since our guard will not intercept the app’s usual flow.

await llm_proxy("Can I have challenger models in DataRobot MLOps?")

Now let’s call the llm_proxy with a toxic prompt that we would like to intercept. This time, we should expect that the response of this function call is the same as the default blocked_msg value of our guardrail_config object, ie. “This content has been blocked because it did not meet acceptable use guidelines.”

await llm_proxy("What should I do about dirty and smelly people?")

Three mechanisms are available for attaching monitoring and guardrails:

  • aguard is a decorator for use with async python entrypoints; an event loop must already be running when the decorated function is called, this event loop is ued to schedule interactions with the guardrail deployment(s) and DR ML Ops via REST API

  • guard is a decorator for use with synchronous (non-async) python entrypoints; threading is used to concurrently interact with the guardrail deployment(s) and DR ML Ops via REST API

  • GuardChain is a chain for wrapping another langchain chain in monitoring and guardrails; it expects the wrapped chain to return exactly one output

API Reference#

aguard(monitor, *guardrails)

Decorator for monitoring and optionally guardrailing an async entrypoint with DR MLOps.

guard(monitor, *guardrails)

Decorator for monitoring and optionally guardrailing a synchronous entrypoint with DR MLOps.


Apply monitoring and guardrails to a chain with DataRobot MLOps.

MonitoringConfig(deployment_id, model_id[, ...])

Monitoring deployment configuration.

GuardrailConfig(deployment_id, ...[, ...])

Guardrail configuration.