list_work_item_acceptance_criteria
Read the ordered, executable definition of done for one card. Each criterion says where to check, any starting state, what action to perform, and the observable result. A zero-length list is a finding: nobody has stated how QA can decide the card is done.
This record as markdown: /tools/adrata-adrata-mcp/list-work-item-acceptance-criteria.md
What list_work_item_acceptance_criteria does on Adrata
AI agents call list_work_item_acceptance_criteria to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_work_item_acceptance_criteria is rated Low
Even though list_work_item_acceptance_criteria only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_work_item_acceptance_criteria 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 list_work_item_acceptance_criteria, this is the rule to start with:
list_work_item_acceptance_criteria is read-only, so it stays allowed. 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 list_work_item_acceptance_criteria call is checked against it from then on.
Questions about list_work_item_acceptance_criteria
Read the ordered, executable definition of done for one card. Each criterion says where to check, any starting state, what action to perform, and the observable result. A zero-length list is a finding: nobody has stated how QA can decide the card is done. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.
Register the Adrata MCP server in PolicyLayer and add a rule for list_work_item_acceptance_criteria: 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.
list_work_item_acceptance_criteria is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_work_item_acceptance_criteria 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 list_work_item_acceptance_criteria. 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.
list_work_item_acceptance_criteria 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