update_shared_report · Clockify Time Tracking MCP

WHAT IT DOES

What update_shared_report does on Clockify Time Tracking

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

WHY IT NEEDS A POLICY

Why update_shared_report needs a policy

The 'update_shared_report' tool performs a reversible write operation—it modifies data (a shared report) without permanently deleting it or executing arbitrary code. Given the context of a time-tracking system where shared reports are used for visibility and analysis, unauthorized updates could affect reporting accuracy and stakeholder trust.

From the tool's definition Tool name 'update_shared_report' indicates modification of an existing report resource. The description is empty, providing no additional detail about scope or side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_shared_report Rate-limited

update_shared_report 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_shared_report": {
      "limits": [
        {
          "counter": "update_shared_report_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 Clockify Time Tracking, so you can run agents against it safely.

FAQ

Questions about update_shared_report

What does the update_shared_report tool do? +

update_shared_report. It is categorised as a Write tool in the Clockify Time Tracking 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_shared_report? +

Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for update_shared_report: 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 Clockify Time Tracking. Nothing to install.

What risk level is update_shared_report? +

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

Can I rate-limit update_shared_report? +

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

Set action: deny in the PolicyLayer policy for update_shared_report. 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_shared_report? +

update_shared_report is provided by the Clockify Time Tracking MCP server (pypi:clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.