Send multiple task directives at once. Use this to queue up multiple tasks for efficient workflow.
AI agents use send_batch_directives to create or update resources in AI Collaboration MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AI Collaboration MCP Server environment.
An AI agent can call send_batch_directives faster than any human can review — one bad instruction and it creates or modifies resources in AI Collaboration MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Send multiple task directives at once. Use this to queue up multiple tasks for efficient workflow. It is categorised as a Write tool in the AI Collaboration MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AI Collaboration MCP Server MCP server in PolicyLayer and add a rule for send_batch_directives: 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 AI Collaboration MCP Server. Nothing to install.
send_batch_directives 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 send_batch_directives 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 send_batch_directives. 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.
send_batch_directives is provided by the AI Collaboration MCP Server MCP server (wyn0001/ai-collab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.