Activate a previously initialized checklist by its goal name or a substring of it. The activated checklist will receive all subsequent task operations.
AI agents use activate_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.
The tool modifies application state (activating a checklist) in a reversible manner by switching context for subsequent operations. While it does not create, retrieve, or delete data directly, it alters the workflow state. This constitutes a Write operation.
From the tool's definition activate_checklist changes the state of a checklist from inactive to active, modifying which checklist receives subsequent operations. This is a state mutation that affects the routing of future task operations.
Attacks that exploit this kind of access
Activate a previously initialized checklist by its goal name or a substring of it. The activated checklist will receive all subsequent task operations. 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 activate_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.
activate_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 activate_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 activate_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.
activate_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 →