send_device_command · Workspace ONE UEM MCP Server MCP

WHAT IT DOES

What send_device_command does on Workspace ONE UEM MCP Server

AI agents use send_device_command 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 send_device_command needs a policy

An AI agent can call send_device_command 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

send_device_command Rate-limited

send_device_command 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": {
    "send_device_command": {
      "limits": [
        {
          "counter": "send_device_command_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 send_device_command

What does the send_device_command tool do? +

send_device_command. 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 send_device_command? +

Register the Workspace ONE UEM MCP Server MCP server in PolicyLayer and add a rule for send_device_command: 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 send_device_command? +

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

Can I rate-limit send_device_command? +

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

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

send_device_command 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.