AI agents call queryClientList to retrieve information from YingDao RPA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context strongly suggest it retrieves a list of clients without modifying, deleting, or executing external operations. The empty description reduces confidence slightly, but the consistent naming convention with other query tools on the server and the absence of any write, delete, or execution keywords indicate this is a data retrieval function with minimal side effects.
From the tool's definition Tool name 'queryClientList' indicates a query/retrieval operation consistent with data retrieval. The description is empty, limiting specificity, but the naming pattern ('query*') aligns with sibling tools like 'queryApplist', 'queryJob', and…
Documented attack patterns abuse exactly the kind of access queryClientList gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and YingDao RPA MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for queryClientList:
{
"version": "1",
"default": "deny",
"tools": {
"queryClientList": {}
}
}queryClientList is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
queryClientList. It is categorised as a Read tool in the YingDao RPA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YingDao RPA MCP Server MCP server in PolicyLayer and add a rule for queryClientList: 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 YingDao RPA MCP Server. Nothing to install.
queryClientList 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 queryClientList 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 queryClientList. 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.
queryClientList is provided by the YingDao RPA MCP Server MCP server (ying-dao/yingdao_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 YingDao RPA MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 YingDao RPA MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.