set_device_name · AutoBot MCP: Risk & Policy

WHAT IT DOES

What set_device_name does on AutoBot MCP

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

WHY IT NEEDS A POLICY

Why set_device_name needs a policy

This tool creates or modifies device metadata (display name) in a reversible manner. It does not delete data, execute arbitrary code, move money, or trigger external side effects beyond renaming the device. The blast radius is minimal: a misleading device name could cause confusion but poses no security or operational risk to the device or its data.

From the tool's definition Tool description states 'Set a display name for the device' — a modification operation that changes device configuration without destructive or irreversible consequences.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_device_name Rate-limited

set_device_name 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": {
    "set_device_name": {
      "limits": [
        {
          "counter": "set_device_name_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 AutoBot MCP, so you can run agents against it safely.

FAQ

Questions about set_device_name

What does the set_device_name tool do? +

Set a display name for the device. It is categorised as a Write tool in the AutoBot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_device_name? +

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

What risk level is set_device_name? +

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

Can I rate-limit set_device_name? +

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

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

set_device_name is provided by the AutoBot MCP server (yz0903/autobot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.