Collect the results and state from all children of a task into a single consolidated view. Provide task_id explicitly. Call this before marking a parent task complete — it gives you a full picture of what each sub-task produced, what was abandoned and why, and what is still pending. Do not comple...
AI agents call synthesize to retrieve information from Conductor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates data from existing task state without modifying, deleting, or executing anything. It is purely informational—a read operation to inspect hierarchical task results before decision-making. The high confidence reflects clear read-only semantics and the absence of side effects.
From the tool's definition Tool collects and consolidates existing results and state from child tasks into a view; uses verbs like 'Collect' and describes querying task state ('what each sub-task produced', 'what was abandoned', 'what is still pending').
Documented attack patterns abuse exactly the kind of access synthesize gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Conductor, and nothing reaches the server without passing your rules. This is the rule we recommend for synthesize:
{
"version": "1",
"default": "deny",
"tools": {
"synthesize": {}
}
}synthesize is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Collect the results and state from all children of a task into a single consolidated view. Provide task_id explicitly. Call this before marking a parent task complete — it gives you a full picture of what each sub-task produced, what was abandoned and why, and what is still pending. Do not complete a parent task without synthesizing first. It is categorised as a Read tool in the Conductor MCP Server, which means it retrieves data without modifying state.
Register the Conductor MCP server in PolicyLayer and add a rule for synthesize: 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 Conductor. Nothing to install.
synthesize 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 synthesize 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 synthesize. 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.
synthesize is provided by the Conductor MCP server (shannonbay/conductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Conductor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Conductor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.