AI agents call upcoming to retrieve information from Dooist without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves upcoming tasks within a specified timeframe from the task management system. It performs a query against stored data and returns results without modifying, deleting, or executing any operations. The blast radius is minimal—an AI agent querying upcoming tasks cannot cause harm through misuse of this specific capability, as it only exposes read access to task metadata.
From the tool's definition Tool name 'upcoming' and description 'Get tasks due in the next N days' indicate a query/retrieval operation with no side effects. The verb 'Get' and the read-only nature of retrieving task data without modification confirm this is a Read operation.
Attacks that exploit this kind of access
Get tasks due in the next N days. It is categorised as a Read tool in the Dooist MCP Server, which means it retrieves data without modifying state.
Register the Dooist MCP server in PolicyLayer and add a rule for upcoming: 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 Dooist. Nothing to install.
upcoming 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 upcoming 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 upcoming. 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.
upcoming is provided by the Dooist MCP server (papermoose/dooist). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
upcoming is one line of Dooist'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 →