get_workspaces

THE RISK

Low Risk

Why get_workspaces needs a policy

This tool retrieves workspace information for the authenticated user without modifying, deleting, or executing any operations. It is a straightforward data query operation, fitting the Read category with low severity since it only exposes existing workspace metadata.

From the tool's definition Tool name 'get_workspaces' and description 'Get all workspaces for the current user' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_workspaces gives an agent:

POLICY

How to control get_workspaces

PolicyLayer is an MCP gateway — it sits between your AI agents and Clockify MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workspaces:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workspaces": {}
  }
}

get_workspaces is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Clockify MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Clockify MCP Server tools

Destructive delete_client Delete a client Destructive delete_project Delete a project Destructive delete_tag Delete a tag Destructive delete_task Delete a task Destructive delete_time_entry Delete a time entry Write stop_time_entry Stop a running time entry Write duplicate_time_entry Duplicate a time entry Write create_client Create a new client

All 29 Clockify MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_workspaces

What does the get_workspaces tool do? +

Get all workspaces for the current user. It is categorised as a Read tool in the Clockify MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workspaces? +

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

What risk level is get_workspaces? +

get_workspaces is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workspaces? +

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

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

get_workspaces is provided by the Clockify MCP Server MCP server (ratheesh-aot/clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clockify MCP Server tool call.

Start from Clockify MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →