add_tag_config_override · Defined MCP: Risk & Policy

WHAT IT DOES

What add_tag_config_override does on Defined

AI agents use add_tag_config_override to create or update resources in Defined — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Defined environment.

WHY IT NEEDS A POLICY

Why add_tag_config_override needs a policy

The tool appears to create or modify (reversibly) a configuration override tied to a tag within the network infrastructure. This is a Write operation because it creates/adds a new configuration state. Severity is medium because misconfiguration of network tags could affect multiple hosts, but the effect is reversible (can be updated or removed).

From the tool's definition Tool name 'add_tag_config_override' suggests creating or modifying a configuration override associated with a tag. The server description indicates this MCP manages Defined Networking infrastructure with host management, tags, and network configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_tag_config_override Rate-limited

add_tag_config_override stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_tag_config_override": {
      "limits": [
        {
          "counter": "add_tag_config_override_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about add_tag_config_override

What does the add_tag_config_override tool do? +

add_tag_config_override. It is categorised as a Write tool in the Defined MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_tag_config_override? +

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

What risk level is add_tag_config_override? +

add_tag_config_override is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_tag_config_override? +

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

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

add_tag_config_override is provided by the Defined MCP server (quickvm/defined-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.