Low Risk

keka_get_payslip

Get payslip for an employee for a specific month and year

Part of the Keka HR Integration Server server.

keka_get_payslip is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE KEKA HR INTEGRATION SERVER →

Free to start. No card required.

AI agents call keka_get_payslip to retrieve information from Keka HR Integration Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though keka_get_payslip only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "keka_get_payslip": {}
  }
}

See the full Keka HR Integration Server policy for all 8 tools.

Get this rule live on your own Keka HR Integration Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY KEKA HR INTEGRATION SERVER →

These attack patterns abuse exactly the kind of access keka_get_payslip gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so keka_get_payslip only ever does what you allow.

SECURE KEKA HR INTEGRATION SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the keka_get_payslip tool do? +

Get payslip for an employee for a specific month and year. It is categorised as a Read tool in the Keka HR Integration Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on keka_get_payslip? +

Register the Keka HR Integration Server MCP server in PolicyLayer and add a rule for keka_get_payslip: 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 Keka HR Integration Server. Nothing to install.

What risk level is keka_get_payslip? +

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

Can I rate-limit keka_get_payslip? +

Yes. Add a rate_limit block to the keka_get_payslip 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 keka_get_payslip completely? +

Set action: deny in the PolicyLayer policy for keka_get_payslip. 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 keka_get_payslip? +

keka_get_payslip is provided by the Keka HR Integration Server MCP server (KaranThink41/keka_official_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Keka HR Integration Server tool call.

Deterministic rules across all 8 Keka HR Integration Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.