task_bulk_add_details
AI agents use task_bulk_add_details to create or update resources in Task Crusader MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Task Crusader MCP environment.
The tool creates or modifies task information at scale ('bulk_add'). This is a Write operation—it changes task state but does not delete or execute arbitrary code. Severity is medium because bulk modifications could affect multiple project tasks, but changes are reversible and limited to task metadata/details within a project management context.
From the tool's definition Tool name 'task_bulk_add_details' indicates creation or modification of task data in bulk. The server context (campaign and task management) and sibling tools like 'campaign_create' and 'campaign_create_with_tasks' confirm this operates within a task/project…
Attacks that exploit this kind of access
task_bulk_add_details. It is categorised as a Write tool in the Task Crusader MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Task Crusader MCP server in PolicyLayer and add a rule for task_bulk_add_details: 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 Task Crusader MCP. Nothing to install.
task_bulk_add_details 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 task_bulk_add_details 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 task_bulk_add_details. 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.
task_bulk_add_details is provided by the Task Crusader MCP server (mcrescenzo/task-crusader-mcp). 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 →