log_time · 7pace Timetracker MCP Server MCP: Risk & Policy

WHAT IT DOES

What log_time does on 7pace Timetracker MCP Server

AI agents use log_time to create or update resources in 7pace Timetracker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 7pace Timetracker MCP Server environment.

WHY IT NEEDS A POLICY

Why log_time needs a policy

The tool creates a new time entry/worklog record, which is a reversible data modification. While it doesn't delete data (which would be Destructive), it does persistently record time allocations that could affect billing, reporting, or resource allocation if misused. The Write category is appropriate as this creates new data in the system.

From the tool's definition Tool name 'log_time' and description 'Log time entry' indicate creation of a new time tracking record. This is a write operation that creates data (a worklog entry) in the 7pace Timetracker system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_time Rate-limited

log_time stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_time": {
      "limits": [
        {
          "counter": "log_time_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches 7pace Timetracker MCP Server, so you can run agents against it safely.

FAQ

Questions about log_time

What does the log_time tool do? +

Log time entry to 7pace Timetracker for a specific work item. It is categorised as a Write tool in the 7pace Timetracker MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_time? +

Register the 7pace Timetracker MCP Server MCP server in PolicyLayer and add a rule for log_time: 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 7pace Timetracker MCP Server. Nothing to install.

What risk level is log_time? +

log_time is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_time? +

Yes. Add a rate_limit block to the log_time 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 log_time completely? +

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

log_time is provided by the 7pace Timetracker MCP Server MCP server (turnono/7pace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.