log_task_time · Jira MCP: Risk & Policy

WHAT IT DOES

What log_task_time does on Jira

AI agents use log_task_time to create or update resources in Jira — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira environment.

WHY IT NEEDS A POLICY

Why log_task_time needs a policy

This tool writes a work log entry to a Jira task, which is a reversible data modification (work logs can typically be edited or deleted). It does not delete data, execute code, or involve financial transactions. The cache invalidation is a side effect of the write operation. Severity is medium because misuse could result in incorrect time tracking records across Jira tasks.

From the tool's definition Log work time to a Jira task. Uses hours and minutes format only (no days). Invalidates cache after logging.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_task_time Rate-limited

log_task_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_task_time": {
      "limits": [
        {
          "counter": "log_task_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 Jira, so you can run agents against it safely.

FAQ

Questions about log_task_time

What does the log_task_time tool do? +

Log work time to a Jira task. Uses hours and minutes format only (no days). Invalidates cache after logging. It is categorised as a Write tool in the Jira 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_task_time? +

Register the Jira MCP server in PolicyLayer and add a rule for log_task_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 Jira. Nothing to install.

What risk level is log_task_time? +

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

Can I rate-limit log_task_time? +

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

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

log_task_time is provided by the Jira MCP server (softspark/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.