log_work_tool · JIRA MCP Server MCP: Risk & Policy

WHAT IT DOES

What log_work_tool does on JIRA MCP Server

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

WHY IT NEEDS A POLICY

Why log_work_tool needs a policy

Logging work on a JIRA issue creates a new worklog record (time entry) associated with the issue. This is a Write operation as it adds data reversibly — worklogs can typically be deleted or edited. It does not delete data, execute code, or involve financial transactions. Severity is medium because misuse could result in incorrect time tracking records across projects, though this is generally reversible.

From the tool's definition 'Log work time on a JIRA issue' — creates a work log entry on an existing issue

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_work_tool Rate-limited

log_work_tool 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_work_tool": {
      "limits": [
        {
          "counter": "log_work_tool_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about log_work_tool

What does the log_work_tool tool do? +

Log work time on a JIRA issue. It is categorised as a Write tool in the JIRA 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_work_tool? +

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

What risk level is log_work_tool? +

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

Can I rate-limit log_work_tool? +

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

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

log_work_tool is provided by the JIRA MCP Server MCP server (klauseduard/vibe-coded-jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.