获取记录详情信息，包括创建者、拥有者、控件信息、根据控件数据类型生成示例值
AI agents call getRecordDetails to retrieve information from MCP Mingdao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only. It fetches existing record metadata and information without creating, modifying, deleting, or executing any operations. The function signature and description show it returns information about records rather than changing state, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'getRecordDetails' and description indicate it retrieves record details including creator, owner, control information, and example values.
Attacks that exploit this kind of access
获取记录详情信息，包括创建者、拥有者、控件信息、根据控件数据类型生成示例值. It is categorised as a Read tool in the MCP Mingdao MCP Server, which means it retrieves data without modifying state.
Register the MCP Mingdao MCP server in PolicyLayer and add a rule for getRecordDetails: 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 MCP Mingdao. Nothing to install.
getRecordDetails 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 getRecordDetails 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 getRecordDetails. 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.
getRecordDetails is provided by the MCP Mingdao MCP server (mingdaocloud/mcp-mingdao). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →