network_condition · AVD MCP Server MCP: Risk & Policy

WHAT IT DOES

What network_condition does on AVD MCP Server

AI agents invoke network_condition to trigger actions in AVD MCP Server. 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 network_condition needs a policy

The tool triggers external operations (network profile application) whose behavioral effects depend on which profile argument is supplied. While it modifies emulator configuration rather than host data, it executes commands that change system state and could affect AI agent testing workflows or inadvertently disrupt network simulation.

From the tool's definition Tool applies network profiles to emulator affecting delay and speed settings ('Aplica perfil de rede no emulador (delay/speed)').

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

network_condition Rate-limited

network_condition 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": {
    "network_condition": {
      "limits": [
        {
          "counter": "network_condition_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 AVD MCP Server, so you can run agents against it safely.

FAQ

Questions about network_condition

What does the network_condition tool do? +

Aplica perfil de rede no emulador (delay/speed) ou perfil avançado. It is categorised as a Execute tool in the AVD MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on network_condition? +

Register the AVD MCP Server MCP server in PolicyLayer and add a rule for network_condition: 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 AVD MCP Server. Nothing to install.

What risk level is network_condition? +

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

Can I rate-limit network_condition? +

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

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

network_condition is provided by the AVD MCP Server MCP server (jramalho/avd-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

network_condition is one line of AVD MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →