Create a new document in a Yuque knowledge base. Args: namespace: Knowledge base namespace. title: Document title. body: Document content (Markdown). slug: URL-friendly slug (auto-generated if empty).
AI agents use yuque_create_doc to create or update resources in autoMate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your autoMate environment.
Creating a new document is a reversible write operation—the document can be edited or deleted later. It modifies state by adding data but does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could result in unwanted documentation being added to a knowledge base, but the impact is contained to a single service and reversible.
From the tool's definition Tool name 'yuque_create_doc' and description explicitly states 'Create a new document' with parameters for namespace, title, body, and slug. This is a create operation that adds new data to a Yuque knowledge base.
Documented attack patterns abuse exactly the kind of access yuque_create_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_create_doc:
{
"version": "1",
"default": "deny",
"tools": {
"yuque_create_doc": {
"limits": [
{
"counter": "yuque_create_doc_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}yuque_create_doc stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new document in a Yuque knowledge base. Args: namespace: Knowledge base namespace. title: Document title. body: Document content (Markdown). slug: URL-friendly slug (auto-generated if empty). It is categorised as a Write tool in the autoMate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the autoMate MCP server in PolicyLayer and add a rule for yuque_create_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_create_doc is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the yuque_create_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_create_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_create_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.