Review the Sanka employee directory. Use this to resolve worker_id values before creating absences, attendance records, or payroll profiles.
AI agents call list_employees to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves employee data for lookup purposes (resolving worker_id values) with no capability to create, modify, delete, or execute operations. It is a pure data retrieval function with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_employees' and description states 'Review the Sanka employee directory' - a read-only operation that retrieves employee information without modification or side effects.
Attacks that exploit this kind of access
Review the Sanka employee directory. Use this to resolve worker_id values before creating absences, attendance records, or payroll profiles. 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_employees: 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_employees 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_employees 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_employees. 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_employees 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.
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 →