deploy_to_adf · Ssis Adf Agent MCP: Risk & Policy

WHAT IT DOES

What deploy_to_adf does on Ssis Adf Agent

AI agents invoke deploy_to_adf to trigger actions in Ssis Adf Agent. 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 IT NEEDS A POLICY

Why deploy_to_adf needs a policy

This tool executes infrastructure-as-code deployment operations against a live Azure Data Factory service. While not immediately destructive, deployment can modify pipelines, schedules, and data flows in production environments, potentially affecting data processing workflows. The severity is high because misuse could disrupt ETL operations and alter data movement across enterprise systems.

From the tool's definition Tool description states it 'Deploy[s] ADF JSON artifacts from a local directory to an Azure Data Factory instance.' Deployment to cloud infrastructure triggers external operations (provisioning, configuration changes, pipeline execution) whose effects depend…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_to_adf Rate-limited

deploy_to_adf stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_to_adf": {
      "limits": [
        {
          "counter": "deploy_to_adf_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ssis Adf Agent, so you can run agents against it safely.

FAQ

Questions about deploy_to_adf

What does the deploy_to_adf tool do? +

Deploy ADF JSON artifacts from a local directory to an Azure Data Factory instance. It is categorised as a Execute tool in the Ssis Adf Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_to_adf? +

Register the Ssis Adf Agent MCP server in PolicyLayer and add a rule for deploy_to_adf: 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 Ssis Adf Agent. Nothing to install.

What risk level is deploy_to_adf? +

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

Can I rate-limit deploy_to_adf? +

Yes. Add a rate_limit block to the deploy_to_adf 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 deploy_to_adf completely? +

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

deploy_to_adf is provided by the Ssis Adf Agent MCP server (tyrrestrup/ssis_adf_agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.