Split oversized or stuck tasks into plan → execute → verify phases. Triggers on estimate >4h or overdue >7 days. Optionally target a specific task by ID.
AI agents use autoSplitTask to create or update resources in Knowledge MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Knowledge MCP Server environment.
This tool modifies existing tasks by splitting them into sub-phases, which is a reversible write operation on the knowledge base (markdown files in a GitHub repo). It creates/updates structured task data but does not delete anything irreversibly, execute code, or involve financial operations.
From the tool's definition Split oversized or stuck tasks into plan → execute → verify phases. Triggers on estimate >4h or overdue >7 days.
Attacks that exploit this kind of access
Split oversized or stuck tasks into plan → execute → verify phases. Triggers on estimate >4h or overdue >7 days. Optionally target a specific task by ID. It is categorised as a Write tool in the Knowledge MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Knowledge MCP Server MCP server in PolicyLayer and add a rule for autoSplitTask: 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 Knowledge MCP Server. Nothing to install.
autoSplitTask 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 autoSplitTask 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 autoSplitTask. 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.
autoSplitTask is provided by the Knowledge MCP Server MCP server (vuluu2k/knowledge_mcp). 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 →