update_worklog_entry · ServiceDesk Plus MCP Server MCP

WHAT IT DOES

What update_worklog_entry does on ServiceDesk Plus MCP Server

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

WHY IT NEEDS A POLICY

Why update_worklog_entry needs a policy

This tool creates or modifies worklog data reversibly. Worklogs are audit-trail records used for tracking technician time and activities on tickets. While modification is possible and could affect historical records or billing calculations, the change can typically be undone or corrected through subsequent updates. This places it in the Write category rather than Destructive.

From the tool's definition update_worklog_entry modifies worklog entries, which are time-tracking and activity records associated with tickets. The description 'Cập nhật worklog entry' (Update worklog entry in Vietnamese) indicates a modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_worklog_entry Rate-limited

update_worklog_entry 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": {
    "update_worklog_entry": {
      "limits": [
        {
          "counter": "update_worklog_entry_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 ServiceDesk Plus MCP Server, so you can run agents against it safely.

FAQ

Questions about update_worklog_entry

What does the update_worklog_entry tool do? +

Cập nhật worklog entry. It is categorised as a Write tool in the ServiceDesk Plus 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 update_worklog_entry? +

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

What risk level is update_worklog_entry? +

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

Can I rate-limit update_worklog_entry? +

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

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

update_worklog_entry is provided by the ServiceDesk Plus MCP Server MCP server (thichcode/servicedeskplus_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.