Get timesheet data for a specific week. Read-only, no side effects. Returns for each entry: - daily_hours: Hours worked each day (monday-saturday) - daily_status: Approval status each day (draft/submitted/approved/rejected) - daily_notes: Notes for each day Status values: - draft: Saved but not s...
AI agents call timecard_get_timesheet to retrieve information from TimeCard MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves timesheet information for a specific week without causing any state changes. It is a straightforward data retrieval operation analogous to a GET request in REST APIs. The explicit documentation confirming read-only behavior and the separation of concerns (changes require timecard_save) confirms this belongs in the Read category with low severity and high confidence.
From the tool's definition Tool description explicitly states 'Read-only, no side effects' and 'This retrieves SAVED data from the server.' The tool only queries and returns timesheet data (daily_hours, daily_status, daily_notes) without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Get timesheet data for a specific week. Read-only, no side effects. Returns for each entry: - daily_hours: Hours worked each day (monday-saturday) - daily_status: Approval status each day (draft/submitted/approved/rejected) - daily_notes: Notes for each day Status values: - draft: Saved but not submitted - submitted: Submitted for approval - approved: Approved by manager - rejected: Rejected by manager This retrieves SAVED data from the server. Use timecard_save to make changes. It is categorised as a Read tool in the TimeCard MCP MCP Server, which means it retrieves data without modifying state.
Register the TimeCard MCP server in PolicyLayer and add a rule for timecard_get_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 TimeCard MCP. Nothing to install.
timecard_get_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 timecard_get_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 timecard_get_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.
timecard_get_timesheet is provided by the TimeCard MCP server (keith-hung/timecard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →