update_device_settings · API-Central MCP: Risk & Policy

WHAT IT DOES

What update_device_settings does on API-Central

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

WHY IT NEEDS A POLICY

Why update_device_settings needs a policy

This tool modifies device configuration metadata (name, location, notes, banner) which are reversible changes. It does not execute arbitrary code, delete data, move money, or perform irreversible operations. The requirement for device_scope_id indicates it operates within defined network scope boundaries.

From the tool's definition Tool performs 'Update device metadata (name, location, notes, banner)' — creates or modifies data reversibly without deletion or financial impact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_device_settings Rate-limited

update_device_settings 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": {
    "update_device_settings": {
      "limits": [
        {
          "counter": "update_device_settings_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 API-Central, so you can run agents against it safely.

FAQ

Questions about update_device_settings

What does the update_device_settings tool do? +

Update device metadata (name, location, notes, banner). device_scope_id required for switch-system path. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_device_settings? +

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

What risk level is update_device_settings? +

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

Can I rate-limit update_device_settings? +

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

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

update_device_settings is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.