DescribeDeviceInfo

SERVERIoacloud SOURCE@ioacloud/ioacloud-mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/ioacloud-ioacloud-mcp/describedeviceinfo.md

WHAT IT DOES

What DescribeDeviceInfo does on Ioacloud

AI agents call DescribeDeviceInfo to retrieve information from Ioacloud without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`Mid`	string	—	终端id
`Type`	string	—	查询类型 process_list network_list service_list
`OsType`	number	—	系统类型（0: win，1：linux，2: mac，4：android，5：ios，-1：全系统（SaaS一体化版本）；不传默认为0）(只支持32位)
`DomainInstanceId`	string	—	管理域实例ID，用于CAM管理域权限分配。若企业未进行管理域的划分，可直接传入根域"1"，此时表示针对当前企业的全部设备和账号进行接口CRUD，具体CRUD的影响范围限制于相应接口的入参。

Parameters from the server's own tool schema.

RISK

Why DescribeDeviceInfo is rated Low

Even though DescribeDeviceInfo only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs DescribeDeviceInfo safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ioacloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For DescribeDeviceInfo, this is the rule to start with:

DescribeDeviceInfo Allowed

DescribeDeviceInfo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "DescribeDeviceInfo": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ioacloud, apply this rule, and every DescribeDeviceInfo call is checked against it from then on.

FAQ

Questions about DescribeDeviceInfo

What does the DescribeDeviceInfo tool do? +

[device] 获取终端进程网络服务信息，私有化调用path为：capi/Assets/Device/DescribeDeviceInfo 获取终端的进程/网络/服务信息。前置：已知 Mid（由 DescribeDevices 提供）。Type 支持 process_list / network_list / service_list。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.

What parameters does DescribeDeviceInfo accept? +

DescribeDeviceInfo accepts 4 parameters: Mid, Type, OsType, DomainInstanceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on DescribeDeviceInfo? +

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

What risk level is DescribeDeviceInfo? +

DescribeDeviceInfo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit DescribeDeviceInfo? +

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

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

DescribeDeviceInfo is provided by the Ioacloud MCP server (@ioacloud/ioacloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ioacloud, and thousands of servers like it.

This server

All 506 Ioacloud tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →