Lists tasks (work packages) in OpenProject, optionally filtered by project ID
AI agents call openproject-list-tasks to retrieve information from OpenProject 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 optional filtering. It performs no modifications, deletions, or external operations. It is a straightforward read operation that returns information without side effects, fitting squarely in the Read category. The low severity reflects minimal risk even if misused by an agent—it can only expose existing data that the authenticated user already has access to.
From the tool's definition Tool name is 'openproject-list-tasks' and description states it 'Lists tasks (work packages) in OpenProject, optionally filtered by project ID'.
Documented attack patterns abuse exactly the kind of access openproject-list-tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenProject MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for openproject-list-tasks:
{
"version": "1",
"default": "deny",
"tools": {
"openproject-list-tasks": {}
}
} openproject-list-tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists tasks (work packages) in OpenProject, optionally filtered by project ID. It is categorised as a Read tool in the OpenProject MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenProject MCP Server MCP server in PolicyLayer and add a rule for openproject-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 OpenProject MCP Server. Nothing to install.
openproject-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 openproject-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 openproject-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.
openproject-list-tasks is provided by the OpenProject MCP Server MCP server (jessebautista/mcp-openproject-smithery). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenProject MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 OpenProject MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.