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

DescribeDataMapRiskPersonDashboard

[dlp] 统计各级风险员工数量 前置:DescribeDataMapByAccount 或 DescribeDLPRiskPersonList 定位风险人员。

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

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

What DescribeDataMapRiskPersonDashboard does on Ioacloud

AI agents call DescribeDataMapRiskPersonDashboard 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
EndTime number Yes 结束时间
BeginTime number Yes 开始时间
Condition object 过滤参数
DomainInstanceId string 管理域实例ID,用于CAM管理域权限分配

Parameters from the server's own tool schema.

Why DescribeDataMapRiskPersonDashboard is rated Low

Even though DescribeDataMapRiskPersonDashboard 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)

Questions about DescribeDataMapRiskPersonDashboard

What does the DescribeDataMapRiskPersonDashboard tool do? +

[dlp] 统计各级风险员工数量 前置:DescribeDataMapByAccount 或 DescribeDLPRiskPersonList 定位风险人员。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.

What parameters does DescribeDataMapRiskPersonDashboard accept? +

DescribeDataMapRiskPersonDashboard accepts 4 parameters: EndTime, BeginTime, Condition, DomainInstanceId. Required: EndTime, BeginTime. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on DescribeDataMapRiskPersonDashboard? +

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

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

Can I rate-limit DescribeDataMapRiskPersonDashboard? +

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

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

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