add_device_tag · Workspace ONE UEM MCP Server MCP

WHAT IT DOES

What add_device_tag does on Workspace ONE UEM MCP Server

AI agents use add_device_tag to create or update resources in Workspace ONE UEM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Workspace ONE UEM MCP Server environment.

WHY IT NEEDS A POLICY

Why add_device_tag needs a policy

An AI agent can call add_device_tag faster than any human can review — one bad instruction and it creates or modifies resources in Workspace ONE UEM MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_device_tag Rate-limited

add_device_tag 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_device_tag": {
      "limits": [
        {
          "counter": "add_device_tag_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 Workspace ONE UEM MCP Server, so you can run agents against it safely.

FAQ

Questions about add_device_tag

What does the add_device_tag tool do? +

Add a tag to a specific device. It is categorised as a Write tool in the Workspace ONE UEM MCP Server 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_device_tag? +

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

What risk level is add_device_tag? +

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

Can I rate-limit add_device_tag? +

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

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

add_device_tag is provided by the Workspace ONE UEM MCP Server MCP server (xyzbuilds/workspace-one-uem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.