attach_device_to_server · Morpheus MCP Server MCP

WHAT IT DOES

What attach_device_to_server does on Morpheus MCP Server

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

WHY IT NEEDS A POLICY

Why attach_device_to_server needs a policy

This tool modifies cloud infrastructure state by dynamically adding hardware to a live server. While reversible (categorizing it as Write rather than Destructive), the impact is high because an AI agent could attach unauthorized devices, disable security controls, or degrade performance.

From the tool's definition Tool description states 'Hotplug a device into a running server' — this creates or modifies the running infrastructure by attaching hardware devices to an active server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

attach_device_to_server Rate-limited

attach_device_to_server 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": {
    "attach_device_to_server": {
      "limits": [
        {
          "counter": "attach_device_to_server_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 Morpheus MCP Server, so you can run agents against it safely.

FAQ

Questions about attach_device_to_server

What does the attach_device_to_server tool do? +

Hotplug a device into a running server. It is categorised as a Write tool in the Morpheus 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 attach_device_to_server? +

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

What risk level is attach_device_to_server? +

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

Can I rate-limit attach_device_to_server? +

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

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

attach_device_to_server is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.