get_employee_schedule
AI agents call get_employee_schedule to retrieve information from Attendance Management MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries employee schedule data with no side effects. No modification, deletion, code execution, or financial impact occurs. Classification as Read is appropriate given the naming convention and the attendance management server context where parallel tools (get_*) are retrieval-only operations.
From the tool's definition Tool name 'get_employee_schedule' and context of sibling read-only tools (get_attendance_records, get_employee_info, get_holidays, get_monthly_attendance_stats) indicate data retrieval.
Attacks that exploit this kind of access
get_employee_schedule. It is categorised as a Read tool in the Attendance Management MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Attendance Management MCP Server MCP server in PolicyLayer and add a rule for get_employee_schedule: 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 Attendance Management MCP Server. Nothing to install.
get_employee_schedule 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 get_employee_schedule 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 get_employee_schedule. 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.
get_employee_schedule is provided by the Attendance Management MCP Server MCP server (shineliang/att-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 →