campaign_create_with_tasks
AI agents use campaign_create_with_tasks 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.
This tool creates new campaigns and tasks, which are reversible write operations. It does not execute external code, delete data irreversibly, or move funds. Severity is medium because misuse could create large numbers of spurious campaigns/tasks requiring cleanup, but the impact is bounded to the task management system and reversible via campaign_delete.
From the tool's definition Tool name 'campaign_create_with_tasks' indicates creation of campaigns and associated tasks. Sibling tools include 'campaign_create' and 'campaign_delete', confirming this server manages campaign/task data.
Attacks that exploit this kind of access
campaign_create_with_tasks. 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 campaign_create_with_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 Task Crusader MCP. Nothing to install.
campaign_create_with_tasks 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 campaign_create_with_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 campaign_create_with_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.
campaign_create_with_tasks 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 →