create_change_time_entry · Freshservice MCP Server MCP

WHAT IT DOES

What create_change_time_entry does on Freshservice MCP Server

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

WHY IT NEEDS A POLICY

Why create_change_time_entry needs a policy

This tool creates a new time entry record linked to a change request—a reversible data modification operation. While the description is empty, the naming convention and context (IT service management for change tracking) suggest it logs time spent on changes, which is a Write operation.

From the tool's definition Tool name 'create_change_time_entry' indicates creation of a new record in the change management system. The server handles 'change requests' and this tool creates time entry data associated with changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_change_time_entry Rate-limited

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

FAQ

Questions about create_change_time_entry

What does the create_change_time_entry tool do? +

create_change_time_entry. It is categorised as a Write tool in the Freshservice 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 create_change_time_entry? +

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

What risk level is create_change_time_entry? +

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

Can I rate-limit create_change_time_entry? +

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

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

create_change_time_entry is provided by the Freshservice MCP Server MCP server (leemangold/freshservice_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.