log_time

Log time spent on a Huly issue. Records a time entry with optional description. Time value is in minutes.

SERVERHuly SOURCEdugynoo/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dugynoo-huly-mcp/log-time.md

WHAT IT DOES

What log_time does on Huly

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

RISK

Why log_time is rated Medium

This tool creates a new time entry record associated with an issue. It writes data (time logs) to the system but does not delete anything or execute code, making Write the appropriate category. Misuse could result in incorrect time tracking records, which is a medium severity concern.

From the tool's definition Log time spent on a Huly issue. Records a time entry with optional description.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs log_time safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log_time, this is the rule to start with:

log_time Rate-limited

log_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_time": {
      "limits": [
        {
          "counter": "log_time_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every log_time call is checked against it from then on.

FAQ

Questions about log_time

What does the log_time tool do? +

Log time spent on a Huly issue. Records a time entry with optional description. Time value is in minutes. It is categorised as a Write tool in the Huly 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_time? +

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

What risk level is log_time? +

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

Can I rate-limit log_time? +

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

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

log_time is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 218 Huly tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →