add_work_item_acceptance_criterion
Add one executable acceptance criterion to a card. This is grooming, not a comment: write where the check runs, the action, the observable result, and its proof route. verificationRoute is REQUIRED -- an omitted route silently became product, which then demands a browser recording for a criterion...
This record as markdown: /tools/adrata-adrata-mcp/add-work-item-acceptance-criterion.md
What add_work_item_acceptance_criterion does on Adrata
AI agents use add_work_item_acceptance_criterion to create or update resources in Adrata, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adrata environment.
Why add_work_item_acceptance_criterion is rated Medium
An AI agent can call add_work_item_acceptance_criterion faster than any human can review: one bad instruction and it creates or modifies resources in Adrata by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs add_work_item_acceptance_criterion safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_work_item_acceptance_criterion, this is the rule to start with:
add_work_item_acceptance_criterion stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every add_work_item_acceptance_criterion call is checked against it from then on.
Questions about add_work_item_acceptance_criterion
Add one executable acceptance criterion to a card. This is grooming, not a comment: write where the check runs, the action, the observable result, and its proof route. verificationRoute is REQUIRED -- an omitted route silently became product, which then demands a browser recording for a criterion about a CI job. engineering and both require a plain-language engineeringReason. The server stores the criterion and its initial route audit receipt atomically.${GOVERNED_NOTE}. It is categorised as a Write tool in the Adrata MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Adrata MCP server in PolicyLayer and add a rule for add_work_item_acceptance_criterion: 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 Adrata. Nothing to install.
add_work_item_acceptance_criterion 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 add_work_item_acceptance_criterion 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 add_work_item_acceptance_criterion. 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.
add_work_item_acceptance_criterion is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adrata, and thousands of servers like it.
This server
Across the catalogue