AI agents call yuque_get_doc 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 'get' verb typically denotes retrieval without modification. Given the autoMate server context where multiple sibling tools follow the pattern of 'get_X' for reads (asana_get_task), this tool almost certainly retrieves a document from Yuque (a collaborative documentation platform). Retrieving a document is a Read operation with minimal blast radius—an AI agent fetching the wrong document has low impact.
From the tool's definition Tool name 'yuque_get_doc' with prefix 'get' indicates a retrieval operation. The 'get_' pattern is consistent with Read operations across the sibling tools (e.g., 'asana_get_task').
Documented attack patterns abuse exactly the kind of access yuque_get_doc 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_get_doc:
{
"version": "1",
"default": "deny",
"tools": {
"yuque_get_doc": {}
}
}yuque_get_doc 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_get_doc. 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_get_doc: 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_get_doc 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_get_doc 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_get_doc. 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_get_doc 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.