log_time_entry

Log time worked on an engagement. Specify hours, description, and whether it

SERVERBusinys SOURCE@businys/mcp-server

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/app-businys-mcp-server/log-time-entry.md

WHAT IT DOES

What log_time_entry does on Businys

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

RISK

Why log_time_entry is rated Medium

This tool creates a new time log record associated with a client engagement. It is a reversible write operation (time entries can typically be deleted or edited). No code execution, financial transaction, or irreversible destruction is involved. Misuse could result in fraudulent billing records, hence medium severity.

From the tool's definition 'Log time worked on an engagement. Specify hours, description' — creates a new time entry record

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs log_time_entry safely

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

log_time_entry Rate-limited

log_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": {
    "log_time_entry": {
      "limits": [
        {
          "counter": "log_time_entry_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 Businys, apply this rule, and every log_time_entry call is checked against it from then on.

FAQ

Questions about log_time_entry

What does the log_time_entry tool do? +

Log time worked on an engagement. Specify hours, description, and whether it. It is categorised as a Write tool in the Businys 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_entry? +

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

What risk level is log_time_entry? +

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

Can I rate-limit log_time_entry? +

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

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

log_time_entry is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Businys, and thousands of servers like it.

This server

All 248 Businys tools →

Across the catalogue

The MCP Attack Database →

Guides

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