campaign_research_update
AI agents use campaign_research_update 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 name contains 'update', which is a write operation that creates or modifies data reversibly. Since the description is empty, confidence is reduced. However, in the context of a task/campaign management system, 'update' operations typically modify records without deletion or irreversible effects.
From the tool's definition Tool name 'campaign_research_update' indicates modification of campaign/research data. The 'update' suffix strongly suggests a write operation that modifies existing records within the task management system.
Attacks that exploit this kind of access
campaign_research_update. 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_research_update: 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_research_update 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_research_update 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_research_update. 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_research_update 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 →