Get details of a specific activity/journal entry
AI agents call get_activity 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 retrieves and queries historical activity/journal data from OpenProject without side effects. It fits the Read category pattern of fetching information for inspection. No data creation, modification, or deletion occurs. The low severity reflects minimal risk even if misused by an AI agent—the worst outcome is information disclosure of activity logs that likely contain non-sensitive operational metadata.
From the tool's definition Tool name 'get_activity' and description 'Get details of a specific activity/journal entry' indicate retrieval of existing data with no modification or deletion capability.
Attacks that exploit this kind of access
Get details of a specific activity/journal entry. 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 get_activity: 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.
get_activity 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_activity 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_activity. 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_activity 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 →