Xem time đã log hôm nay. Gọi trước khi log để tránh log trùng.
AI agents call get_today_time_log to retrieve information from Redmine 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 time log records for the current day to prevent duplicate entries. It performs a read-only query operation with no side effects, reversible actions, or state changes. The blast radius of misuse is minimal as it only exposes already-logged time data.
From the tool's definition Tool description states 'Xem time đã log hôm nay' (View time logged today) and 'Gọi trước khi log để tránh log trùng' (Call before logging to avoid duplicate logging). The action is purely retrieving/viewing existing time log data without modification.
Attacks that exploit this kind of access
Xem time đã log hôm nay. Gọi trước khi log để tránh log trùng. It is categorised as a Read tool in the Redmine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redmine MCP Server MCP server in PolicyLayer and add a rule for get_today_time_log: 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 Redmine MCP Server. Nothing to install.
get_today_time_log 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_today_time_log 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_today_time_log. 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_today_time_log is provided by the Redmine MCP Server MCP server (tuantrunglc/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 →