New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

DescribeDeviceHardwareInfoList

[device] 查询满足条件的查询终端硬件信息列表,私有化调用path为:/capi/Assets/Device/DescribeDeviceHardwareInfoList GroupId 和 OsType 必填且必须匹配。前置:DescribeRootGroupId 或 DescribeDeviceChildGroups。

SERVERIoacloud SOURCE@ioacloud/ioacloud-mcp
Low RISK CLASS
Category Read
Parameters 52 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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

What DescribeDeviceHardwareInfoList does on Ioacloud

AI agents call DescribeDeviceHardwareInfoList 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.

ParameterTypeRequiredDescription
OsType number Yes 【必填】系统类型(0: win,1:linux,2: mac,4:android,5:ios,-1:全系统(SaaS一体化版本))(只支持32位),需要和GroupId或者GroupIds匹配枚举值:0: Windows1: Linux2: macOS4: Android5: iOS-1: 全系统(SaaS一体化版本)
GroupId number Yes 【必填】设备分组id(需要和OsType匹配),下面是私有化场景下默认id:id-名称-操作系统1 全网终端 Win2 未分组终端 Win30000000 服务器 Win40000101 全网终端 Linux40000102 未分组终端 Linux40000103 服务器 Linux40000201 全网终端 macO
MidList array 设备唯一标识符列表
Condition object 过滤条件参数(字段含义请参考接口返回值) - Name, 类型String,支持操作:【eq,like,ilike】,支持排序 - UserName, 类型String,支持操作:【eq,like,ilike】,支持排序 - IoaUserName,类型String,支持操作:【eq,like,ilike】,支持排序
DomainInstanceId string 管理域实例ID,用于CAM管理域权限分配。若企业未进行管理域的划分,可直接传入根域"1",此时表示针对当前企业的全部设备和账号进行接口CRUD,具体CRUD的影响范围限制于相应接口的入参。

Parameters from the server's own tool schema.

Why DescribeDeviceHardwareInfoList is rated Low

Even though DescribeDeviceHardwareInfoList 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.

Risk signalsHigh parameter count (29 properties)

Questions about DescribeDeviceHardwareInfoList

What does the DescribeDeviceHardwareInfoList tool do? +

[device] 查询满足条件的查询终端硬件信息列表,私有化调用path为:/capi/Assets/Device/DescribeDeviceHardwareInfoList GroupId 和 OsType 必填且必须匹配。前置:DescribeRootGroupId 或 DescribeDeviceChildGroups。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.

What parameters does DescribeDeviceHardwareInfoList accept? +

DescribeDeviceHardwareInfoList accepts 5 parameters: OsType, GroupId, MidList, Condition, DomainInstanceId. Required: OsType, GroupId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on DescribeDeviceHardwareInfoList? +

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

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

Can I rate-limit DescribeDeviceHardwareInfoList? +

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

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

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

More on Ioacloud, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ioacloud's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.