Initialize a new task checklist for the current subconductor run. This tool creates a task table with Status, ID, Name, and optional custom columns. It also natively sets up goal tracking to monitor completion progress.
AI agents use init_checklist to create or update resources in Subconductor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Subconductor environment.
This tool creates a new checklist/table structure in the persistent state machine. It is a Write operation (reversible creation of structured data), with low severity since it only initializes a checklist and does not delete, execute code, or involve finances.
From the tool's definition Initialize a new task checklist... creates a task table with Status, ID, Name, and optional custom columns
Attacks that exploit this kind of access
Initialize a new task checklist for the current subconductor run. This tool creates a task table with Status, ID, Name, and optional custom columns. It also natively sets up goal tracking to monitor completion progress. It is categorised as a Write tool in the Subconductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Subconductor MCP server in PolicyLayer and add a rule for init_checklist: 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 Subconductor. Nothing to install.
init_checklist 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 init_checklist 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 init_checklist. 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.
init_checklist is provided by the Subconductor MCP server (paulbenchea/mcp-subconductor). 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 →