AI agents call query_timesheet to retrieve information from Workhour without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries timesheet data with optional filtering parameters but performs no side effects, data modification, or irreversible actions. It is a read-only query operation, representing minimal risk even if invoked by an AI agent with incorrect parameters—the worst outcome would be retrieval of unintended but harmless data.
From the tool's definition Tool name 'query_timesheet' and description '查询工时填报记录' (query timesheet records) indicates data retrieval. Parameters allow filtering by person, project, and time range, with default scope of current user's past 30 days.
Attacks that exploit this kind of access
查询工时填报记录（按人/项目/时间范围；不传则当前用户近30天）。. It is categorised as a Read tool in the Workhour MCP Server, which means it retrieves data without modifying state.
Register the Workhour MCP server in PolicyLayer and add a rule for query_timesheet: 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 Workhour. Nothing to install.
query_timesheet 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 query_timesheet 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 query_timesheet. 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.
query_timesheet is provided by the Workhour MCP server (Calvin-Ca/workhour-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
query_timesheet is one line of Workhour's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →