list_employees

Review the Sanka employee directory. Use this to resolve worker_id values before creating absences, attendance records, or payroll profiles.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/list-employees.md

WHAT IT DOES

What list_employees does on Sanka MCP Server

AI agents call list_employees 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.

RISK

Why list_employees is rated Low

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

RECOMMENDED RULE

The rule that runs list_employees 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_employees, this is the rule to start with:

list_employees Allowed

list_employees is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_employees": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every list_employees call is checked against it from then on.

FAQ

Questions about list_employees

What does the list_employees tool do? +

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.

How do I enforce a policy on list_employees? +

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.

What risk level is list_employees? +

list_employees is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_employees? +

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.

How do I block list_employees completely? +

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.

What MCP server provides list_employees? +

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.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →