list_attendance_records
Review Sanka work attendance records. This is for employee attendance/time tracking, not public calendar attendance bookings.
This record as markdown: /tools/sankahq-sanka-mcp/list-attendance-records.md
What list_attendance_records does on Sanka MCP Server
AI agents call list_attendance_records to retrieve information from Sanka 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_attendance_records is rated Low
The tool retrieves and queries employee attendance/time tracking data. The verb 'Review' and 'list' both indicate read-only data retrieval operations. While attendance data may be sensitive in a business context, the tool itself performs no writes, deletions, or external state changes. The blast radius if misused is limited to potential information disclosure, classified as low severity for a read operation.
From the tool's definition Tool name 'list_attendance_records' and description explicitly states 'Review' attendance records, which is a retrieval operation with no modification capability mentioned.
Attacks that exploit this kind of access
The rule that runs list_attendance_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_attendance_records, this is the rule to start with:
list_attendance_records 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 Sanka MCP Server, apply this rule, and every list_attendance_records call is checked against it from then on.
Questions about list_attendance_records
Review Sanka work attendance records. This is for employee attendance/time tracking, not public calendar attendance bookings. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_attendance_records: 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 Sanka MCP Server. Nothing to install.
list_attendance_records 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_attendance_records 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_attendance_records. 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_attendance_records is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue