This record as markdown: /tools/funny-booth-aos-mcp-server/delete-backlog-item.md
What delete_backlog_item does on Aos
AI agents call delete_backlog_item to permanently remove resources in Aos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | バックログID |
Parameters from the server's own tool schema.
Why delete_backlog_item is rated Critical
The 'delete' verb paired with a business artifact (backlog_item) indicates this tool permanently removes data without the ability to undo or recover it. This is a classic destructive operation. Even without a description, the naming convention clearly establishes this as Destructive rather than Write.
From the tool's definition Tool name is 'delete_backlog_item' with 'delete' prefix, indicating irreversible removal of data. No description provided, but the name unambiguously signals a destructive operation.
Attacks that exploit this kind of access
The rule that runs delete_backlog_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_backlog_item, this is the rule to start with:
delete_backlog_item is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every delete_backlog_item call is checked against it from then on.
Questions about delete_backlog_item
delete_backlog_item is a destructive tool on the Aos MCP server. It is categorised as a Destructive tool in the Aos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_backlog_item accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Aos MCP server in PolicyLayer and add a rule for delete_backlog_item: 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 Aos. Nothing to install.
delete_backlog_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_backlog_item 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 delete_backlog_item. 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.
delete_backlog_item is provided by the Aos MCP server (@funny-booth/aos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
Across the catalogue