Get tasks from a all boards. Can filtered by q (query to filter task name), board_id, project_id, deadline_from (Unix timestamp in seconds), deadline_to (Unix timestamp in seconds), created_from (Unix timestamp in seconds), created_to (Unix timestamp in seconds), page (page number), creator (user...
AI agents call get_tasks to retrieve information from Rework 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 with various filter options but performs no side effects. It is a straightforward data retrieval operation typical of Read category tools. The filtering parameters do not change any state. Severity is low because unauthorized access to task metadata poses minimal risk compared to other categories.
From the tool's definition Tool description explicitly states 'Get tasks from all boards' with filtering parameters (query, board_id, project_id, deadline, created date, page, creator, assignee, status).
Attacks that exploit this kind of access
Get tasks from a all boards. Can filtered by q (query to filter task name), board_id, project_id, deadline_from (Unix timestamp in seconds), deadline_to (Unix timestamp in seconds), created_from (Unix timestamp in seconds), created_to (Unix timestamp in seconds), page (page number), creator (user id of creator), assign (user id of assignee), status (one of:. It is categorised as a Read tool in the Rework MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rework MCP Server MCP server in PolicyLayer and add a rule for get_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 Rework MCP Server. Nothing to install.
get_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 get_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 get_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.
get_tasks is provided by the Rework MCP Server MCP server (rework-com/rework-mcp-server). 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 →