AI agents call yuque_list_docs to retrieve information from autoMate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name pattern 'list_*' strongly suggests a retrieval operation that queries and returns a collection of documents. The empty description reduces confidence slightly, but the naming convention and the context of similar sibling tools (airtable_list_records, amap_search_poi) on this multi-integration server confirm this is a read operation. No modification, deletion, execution, or financial impact is indicated.
From the tool's definition Tool name 'yuque_list_docs' indicates a list operation on Yuque documents. 'List' operations are query-based and retrieve data without side effects.
Documented attack patterns abuse exactly the kind of access yuque_list_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for yuque_list_docs:
{
"version": "1",
"default": "deny",
"tools": {
"yuque_list_docs": {}
}
}yuque_list_docs 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.
yuque_list_docs. It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.
Register the autoMate MCP server in PolicyLayer and add a rule for yuque_list_docs: 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 autoMate. Nothing to install.
yuque_list_docs 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 yuque_list_docs 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 yuque_list_docs. 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.
yuque_list_docs is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.