sangfor.dry_run_product_change · Sangfor Mcp Workflow MCP

WHAT IT DOES

What sangfor.dry_run_product_change does on Sangfor Mcp Workflow

AI agents invoke sangfor.dry_run_product_change to trigger actions in Sangfor Mcp Workflow. 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 sangfor.dry_run_product_change needs a policy

This tool triggers execution of product changes (even in dry-run mode), which can affect system behavior and configuration. The dry-run nature mitigates some severity (not directly destructive), but it still represents code/configuration execution with potential side effects depending on what changes are simulated.

From the tool's definition Tool name contains 'dry_run_product_change' — indicates execution of product changes in a test mode. The 'dry_run' prefix suggests trial execution of configuration or deployment actions, and 'product_change' indicates modifications to Sangfor Engineer systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sangfor.dry_run_product_change Rate-limited

sangfor.dry_run_product_change 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": {
    "sangfor.dry_run_product_change": {
      "limits": [
        {
          "counter": "sangfor.dry_run_product_change_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 Sangfor Mcp Workflow, so you can run agents against it safely.

FAQ

Questions about sangfor.dry_run_product_change

What does the sangfor.dry_run_product_change tool do? +

sangfor.dry_run_product_change. It is categorised as a Execute tool in the Sangfor Mcp Workflow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sangfor.dry_run_product_change? +

Register the Sangfor Mcp Workflow MCP server in PolicyLayer and add a rule for sangfor.dry_run_product_change: 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 Sangfor Mcp Workflow. Nothing to install.

What risk level is sangfor.dry_run_product_change? +

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

Can I rate-limit sangfor.dry_run_product_change? +

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

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

sangfor.dry_run_product_change is provided by the Sangfor Mcp Workflow MCP server (whelp99-code/sangfor-mcp-workflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.