Retrieve a batch of multiple pending tasks from the active checklist. Tasks are returned with an ID (e.g.,
AI agents call get_pending_tasks to retrieve information from Subconductor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing task data from a checklist without creating, modifying, deleting, or executing any operations. It is a simple data retrieval function with no destructive or side-effect-producing capabilities. Misuse would have minimal blast radius—an agent could read task information but cannot alter system state or cause harm.
From the tool's definition Tool name is 'get_pending_tasks' and description states 'Retrieve a batch of multiple pending tasks from the active checklist.' The verb 'Retrieve' and the action of returning task data indicates read-only access with no modification or side effects.
Attacks that exploit this kind of access
Retrieve a batch of multiple pending tasks from the active checklist. Tasks are returned with an ID (e.g.,. It is categorised as a Read tool in the Subconductor MCP Server, which means it retrieves data without modifying state.
Register the Subconductor MCP server in PolicyLayer and add a rule for get_pending_tasks: 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.
get_pending_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_pending_tasks 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 get_pending_tasks. 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.
get_pending_tasks 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 →