Execute multiple tasks in parallel on a pool.
AI agents invoke execute_batch_on_pool to trigger actions in Session Buddy. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers execution of arbitrary tasks on external resources (a pool). While the description doesn't specify what types of tasks or their scope, the core function is to run code/operations whose side effects are determined by caller-provided task definitions.
From the tool's definition Tool name 'execute_batch_on_pool' and description 'Execute multiple tasks in parallel on a pool' directly indicate code/task execution.
Attacks that exploit this kind of access
Execute multiple tasks in parallel on a pool. It is categorised as a Execute tool in the Session Buddy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Session Buddy MCP server in PolicyLayer and add a rule for execute_batch_on_pool: 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 Session Buddy. Nothing to install.
execute_batch_on_pool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_batch_on_pool 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 execute_batch_on_pool. 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.
execute_batch_on_pool is provided by the Session Buddy MCP server (lesleslie/session-buddy). 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 →