add_time_worked_tool · MCP Request-tracker MCP

WHAT IT DOES

What add_time_worked_tool does on MCP Request-tracker

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

WHY IT NEEDS A POLICY

Why add_time_worked_tool needs a policy

This tool creates or modifies time-tracking records associated with tickets. While reversible (time entries can typically be corrected or removed), it writes data that affects ticket management, billing reconciliation, and work hour reporting.

From the tool's definition Tool name 'add_time_worked_tool' and description 'Add time to the time worked on a ticket' indicate modification of ticket metadata (time tracking data).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_time_worked_tool Rate-limited

add_time_worked_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": {
    "add_time_worked_tool": {
      "limits": [
        {
          "counter": "add_time_worked_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 MCP Request-tracker, so you can run agents against it safely.

FAQ

Questions about add_time_worked_tool

What does the add_time_worked_tool tool do? +

Add time to the time worked on a ticket. It is categorised as a Write tool in the MCP Request-tracker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_time_worked_tool? +

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

What risk level is add_time_worked_tool? +

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

Can I rate-limit add_time_worked_tool? +

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

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

add_time_worked_tool is provided by the MCP Request-tracker MCP server (crunchtools/mcp-request-tracker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.