// MCP TOOL REFERENCE

TRACKING TIME MCP TOOLS

8 tools from the Tracking Time MCP MCP Server, categorised by risk level.

READ TOOLS

mcp_customers_list List customers. Call mcp_get_me first to determine account context. mcp_events_get Get a single event by ID. Call mcp_get_me first to determine account context. mcp_events_list Retrieves a list of events. Call mcp_get_me first to determine account context. To filter by a specific entity (e.g. Project), set 'filter' to the ... mcp_get_me Get current user profile information. Call this first to establish account/user context before using other tools. mcp_projects_list List projects. Call mcp_get_me first to determine account context. mcp_services_list List services. Call mcp_get_me first to determine account context. mcp_tasks_list List tasks. Call mcp_get_me first to determine account context. mcp_users_list List users in the account. Call mcp_get_me first to determine account context.

// FAQ

How many tools does the Tracking Time MCP MCP server have? +

The Tracking Time MCP MCP server exposes 8 tools across 1 categories: Read.

How do I enforce policies on Tracking Time MCP tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Tracking Time MCP server.

What risk categories do Tracking Time MCP tools fall into? +

Tracking Time MCP tools are categorised as Read (8). Each category has a recommended default policy.

Enforce policies on Tracking Time MCP

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →