assign_device_to_site · API-Central MCP: Risk & Policy

WHAT IT DOES

What assign_device_to_site does on API-Central

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

The tool modifies the configuration state of network infrastructure by changing site assignments. While this affects network operations and could impact service delivery if misused, it is reversible and does not delete data or execute arbitrary code. The blast radius is moderate—incorrect assignments could disrupt network topology or service access, but the action can be undone by reassigning the device.

From the tool's definition Assign or move a device to a site. This operation creates or modifies the association between a network device and a site location, which is reversible (the device can be moved to a different site or unassigned).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_device_to_site Rate-limited

assign_device_to_site 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": {
    "assign_device_to_site": {
      "limits": [
        {
          "counter": "assign_device_to_site_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 assign_device_to_site

What does the assign_device_to_site tool do? +

Assign or move a device to a site. device_type hint: SWITCH/AP/GATEWAY. 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 assign_device_to_site? +

Register the API-Central MCP server in PolicyLayer and add a rule for assign_device_to_site: 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 assign_device_to_site? +

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

Can I rate-limit assign_device_to_site? +

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

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

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