Low Risk

show_time_entry

Get details of a time record.

How to control show_time_entry ↓

AI agents call show_time_entry 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.

Low Risk

This tool retrieves and displays information about an existing time entry record. It performs a query operation without modifying, executing, or deleting any data. The verb 'Get details of' clearly indicates a read-only action. Given the Redmine context, this would typically be a GET API call to retrieve time entry metadata.

From the tool's definition Tool name 'show_time_entry' and description 'Get details of a time record' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access show_time_entry gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Redmine MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for show_time_entry:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "show_time_entry": {}
  }
}

show_time_entry is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Redmine MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the show_time_entry tool do? +

Get details of a time record. It is categorised as a Read tool in the Redmine MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on show_time_entry? +

Register the Redmine MCP Server MCP server in PolicyLayer and add a rule for show_time_entry: 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.

What risk level is show_time_entry? +

show_time_entry is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit show_time_entry? +

Yes. Add a rate_limit block to the show_time_entry 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.

How do I block show_time_entry completely? +

Set action: deny in the PolicyLayer policy for show_time_entry. 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.

What MCP server provides show_time_entry? +

show_time_entry is provided by the Redmine MCP Server MCP server (yonaka15/mcp-server-redmine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Redmine MCP Server tool call.

Deterministic rules across all 26 Redmine MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 Redmine MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.