task_acceptance_criteria_update
AI agents use task_acceptance_criteria_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.
This tool creates or modifies acceptance criteria for tasks within campaigns—a reversible write operation. The empty description prevents higher confidence, but the naming pattern ('update' suffix) and sibling tools (campaign_create, campaign_delete) establish this as a Write operation rather than Execute or Destructive.
From the tool's definition Tool name 'task_acceptance_criteria_update' indicates it modifies task acceptance criteria. The 'update' verb and lack of 'delete' terminology suggest reversible modification of campaign/task metadata.
Attacks that exploit this kind of access
task_acceptance_criteria_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 task_acceptance_criteria_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.
task_acceptance_criteria_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 task_acceptance_criteria_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 task_acceptance_criteria_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.
task_acceptance_criteria_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 →