List tasks from Dooray project with optional filtering
AI agents call dooray_list_tasks to retrieve information from Dooray MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries task data from Dooray with optional filters. It has no side effects, does not modify data, execute code, delete records, or create financial obligations. It is a straightforward read operation that matches the 'Read' category definition of retrieving or querying data without side effects.
From the tool's definition Tool name contains 'list' and description states 'List tasks from Dooray project with optional filtering' — pure retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List tasks from Dooray project with optional filtering. It is categorised as a Read tool in the Dooray MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dooray MCP Server MCP server in PolicyLayer and add a rule for dooray_list_tasks: 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 Dooray MCP Server. Nothing to install.
dooray_list_tasks 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 dooray_list_tasks 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 dooray_list_tasks. 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.
dooray_list_tasks is provided by the Dooray MCP Server MCP server (kwanok/dooray-mcp). 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 →