WRITE/LOCAL. Explicitly acknowledges one or more durable task-event ids and removes them from the pending spool. Unknown ids are reported without failing known acknowledgements.
AI agents use acknowledge_task_events to create or update resources in Agentic Task System — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agentic Task System environment.
This tool modifies state by removing acknowledged events from a pending spool. While it involves deletion, the operation is scoped to local queue management (not destructive to core data), is reversible through event logs, and operates on ephemeral queue state rather than permanent data deletion. The 'WRITE/LOCAL' annotation in the description confirms write-category classification.
From the tool's definition Tool description explicitly states 'WRITE/LOCAL' and describes removing items from a pending spool (modifying state reversibly).
Attacks that exploit this kind of access
WRITE/LOCAL. Explicitly acknowledges one or more durable task-event ids and removes them from the pending spool. Unknown ids are reported without failing known acknowledgements. It is categorised as a Write tool in the Agentic Task System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agentic Task System MCP server in PolicyLayer and add a rule for acknowledge_task_events: 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 Agentic Task System. Nothing to install.
acknowledge_task_events 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 acknowledge_task_events 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 acknowledge_task_events. 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.
acknowledge_task_events is provided by the Agentic Task System MCP server (renezander030/agentic-task-system). 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 →