WRITE/LOCAL. Creates or replaces the local corpus-diff event checkpoint. This only observes task state; it never launches an agent or performs an external action.
AI agents use snapshot_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.
The tool writes/replaces a local checkpoint file or record. It is reversible in nature (a checkpoint can be overwritten again) and confined to local state with no external actions, making Write the appropriate category at low severity.
From the tool's definition 'Creates or replaces the local corpus-diff event checkpoint' and 'WRITE/LOCAL' prefix indicate a write operation; 'only observes task state; it never launches an agent or performs an external action' confirms no execution or destructive side effects
Attacks that exploit this kind of access
WRITE/LOCAL. Creates or replaces the local corpus-diff event checkpoint. This only observes task state; it never launches an agent or performs an external action. 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 snapshot_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.
snapshot_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 snapshot_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 snapshot_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.
snapshot_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 →