List members of the project that owns a work package
AI agents call list_work_package_members to retrieve information from Tonle 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 queries and returns a list of members associated with a work package's project. It is a read-only operation that retrieves data without creating, modifying, deleting, or executing any side effects. The verb 'list' and the absence of any language indicating state changes confirms this is a Read category tool.
From the tool's definition Tool name 'list_work_package_members' and description 'List members of the project that owns a work package' indicate a retrieval operation with no modification or destructive intent.
Attacks that exploit this kind of access
List members of the project that owns a work package. It is categorised as a Read tool in the Tonle OpenProject MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tonle OpenProject MCP Server MCP server in PolicyLayer and add a rule for list_work_package_members: 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 Tonle OpenProject MCP Server. Nothing to install.
list_work_package_members 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_work_package_members 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_work_package_members. 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_work_package_members is provided by the Tonle OpenProject MCP Server MCP server (liratanak/openproject-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 →