task_acceptance_criteria_add
AI agents use task_acceptance_criteria_add 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 adds acceptance criteria to tasks, which is a reversible write operation that modifies task metadata. No deletion, code execution, or financial impact is indicated. Severity is medium because incorrect criteria could affect project planning, but changes are reversible and the blast radius is limited to task documentation.
From the tool's definition Tool name 'task_acceptance_criteria_add' indicates creation or modification of acceptance criteria data associated with tasks. The server context involves task and campaign management. The suffix '_add' suggests data creation/modification.
Attacks that exploit this kind of access
task_acceptance_criteria_add. 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_add: 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_add 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_add 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_add. 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_add 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 →