Read-only. Lists durable task-event envelopes that have not been acknowledged by a consumer. Task bodies are not stored in the spool.
AI agents call list_pending_task_events to retrieve information from Agentic Task System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries pending task events without creating, modifying, or deleting anything. It is a pure read operation that retrieves state information about task events. The low severity reflects that accessing a list of pending events has minimal blast radius and no irreversible effects.
From the tool's definition The tool is explicitly described as 'Read-only' and 'Lists durable task-event envelopes that have not been acknowledged by a consumer.' It retrieves data without modification.
Attacks that exploit this kind of access
Read-only. Lists durable task-event envelopes that have not been acknowledged by a consumer. Task bodies are not stored in the spool. It is categorised as a Read tool in the Agentic Task System MCP Server, which means it retrieves data without modifying state.
Register the Agentic Task System MCP server in PolicyLayer and add a rule for list_pending_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.
list_pending_task_events 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_pending_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 list_pending_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.
list_pending_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.
list_pending_task_events is one line of Agentic Task System's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →