Create a task. Complexity determines review requirements: simple=no review, medium=verify on completion, complex/critical=planner approval required. Isolation determines whether implementer works in shared directory or isolated git worktree.
AI agents use task_create to create or update resources in Lockstep — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lockstep environment.
This tool creates task objects in a coordination system, reversibly modifying shared project state. While task creation could indirectly trigger workflows or commands via other tools (like command_run), the task_create tool itself only writes metadata.
From the tool's definition Tool description states 'Create a task' - a write operation that creates new data structures. The tool does not delete, execute code, or move money.
Attacks that exploit this kind of access
Create a task. Complexity determines review requirements: simple=no review, medium=verify on completion, complex/critical=planner approval required. Isolation determines whether implementer works in shared directory or isolated git worktree. It is categorised as a Write tool in the Lockstep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lockstep MCP server in PolicyLayer and add a rule for task_create: 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 Lockstep. Nothing to install.
task_create 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 task_create 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 task_create. 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.
task_create is provided by the Lockstep MCP server (tmmoore286/lockstep-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 →