list_timeclock
List technician time clock entries via POST /timesheet/search. userId and locationId are sent to the API. Shopmonkey documents no date filter for time clock, so startDate/endDate are applied client-side on each entry\
This record as markdown: /tools/abbottdevelopments-shopmonkey-mcp-server/list-timeclock.md
What list_timeclock does on Shopmonkey MCP Server
AI agents call list_timeclock to retrieve information from Shopmonkey MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_timeclock is rated Low
Retrieves timesheet data without modification; client-side filtering poses no execution risk.
From the tool's definition List technician time clock entries via POST /timesheet/search
Attacks that exploit this kind of access
The rule that runs list_timeclock safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Shopmonkey MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_timeclock, this is the rule to start with:
list_timeclock is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Shopmonkey MCP Server, apply this rule, and every list_timeclock call is checked against it from then on.
Questions about list_timeclock
List technician time clock entries via POST /timesheet/search. userId and locationId are sent to the API. Shopmonkey documents no date filter for time clock, so startDate/endDate are applied client-side on each entry\. It is categorised as a Read tool in the Shopmonkey MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shopmonkey MCP Server MCP server in PolicyLayer and add a rule for list_timeclock: 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 Shopmonkey MCP Server. Nothing to install.
list_timeclock is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_timeclock 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.
Set action: deny in the PolicyLayer policy for list_timeclock. 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.
list_timeclock is provided by the Shopmonkey MCP Server MCP server (abbottdevelopments/shopmonkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Shopmonkey MCP Server, and thousands of servers like it.
This server
Across the catalogue