List tasks in the project
AI agents call list_tasks to retrieve information from Cross-Project MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns task data without creating, modifying, deleting, or executing any operations. The sibling tools (find_files, read_file, search_code, list_directory) are all Read operations, and list_tasks fits that same pattern. The blast radius of listing tasks is minimal — it only exposes existing task metadata.
From the tool's definition Tool name is 'list_tasks' and description states 'List tasks in the project' — a retrieval operation with no modification or side effects. Aligns with the Read category pattern of retrieve/query operations.
Attacks that exploit this kind of access
List tasks in the project. It is categorised as a Read tool in the Cross-Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cross-Project MCP Server MCP server in PolicyLayer and add a rule for 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 Cross-Project MCP Server. Nothing to install.
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 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 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.
list_tasks is provided by the Cross-Project MCP Server MCP server (sweetsrepo/cross-project-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 →