DescribeScanVirusTaskDeviceDetail
[incident] 查询特定病毒扫描任务下的特定终端的具体病毒查杀情况 前置：拿 TaskId + Mid。
This record as markdown: /tools/ioacloud-ioacloud-mcp/describescanvirustaskdevicedetail.md
What DescribeScanVirusTaskDeviceDetail does on Ioacloud
AI agents call DescribeScanVirusTaskDeviceDetail 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 | Yes | 设备标识码 |
Condition | object | — | 支持的过滤字段： - VirusType: 病毒类型 - FixResult: 病毒处理状态（1 清除成功，2 清除失败，3 添加信任，4 未处理） |
ScanVirusTaskID | number | Yes | 病毒扫描任务 ID病毒扫描任务 ID |
DomainInstanceId | string | — | 管理域实例ID，用于CAM管理域权限分配。若企业未进行管理域的划分，可直接传入根域"1"，此时表示针对当前企业的全部设备和账号进行接口CRUD，具体CRUD的影响范围限制于相应接口的入参。 |
Parameters from the server's own tool schema.
Why DescribeScanVirusTaskDeviceDetail is rated Low
Even though DescribeScanVirusTaskDeviceDetail 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 (28 properties)
Attacks that exploit this kind of access
The rule that runs DescribeScanVirusTaskDeviceDetail 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 DescribeScanVirusTaskDeviceDetail, this is the rule to start with:
DescribeScanVirusTaskDeviceDetail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ioacloud, apply this rule, and every DescribeScanVirusTaskDeviceDetail call is checked against it from then on.
Questions about DescribeScanVirusTaskDeviceDetail
[incident] 查询特定病毒扫描任务下的特定终端的具体病毒查杀情况 前置：拿 TaskId + Mid。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeScanVirusTaskDeviceDetail accepts 4 parameters: Mid, Condition, ScanVirusTaskID, DomainInstanceId. Required: Mid, ScanVirusTaskID. The full parameter table on this page comes from the server's own tool schema.
Register the Ioacloud MCP server in PolicyLayer and add a rule for DescribeScanVirusTaskDeviceDetail: 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.
DescribeScanVirusTaskDeviceDetail is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the DescribeScanVirusTaskDeviceDetail 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.
Set action: deny in the PolicyLayer policy for DescribeScanVirusTaskDeviceDetail. 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.
DescribeScanVirusTaskDeviceDetail 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.
This server
Across the catalogue