lever_archive_candidate · Lever ATS MCP Server MCP

WHAT IT DOES

What lever_archive_candidate does on Lever ATS MCP Server

AI agents use lever_archive_candidate to create or update resources in Lever ATS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lever ATS MCP Server environment.

WHY IT NEEDS A POLICY

Why lever_archive_candidate needs a policy

This tool modifies candidate data by changing their status to archived. While archival is a significant action in recruitment workflows, it is reversible—archived candidates can be restored. This places it in the Write category rather than Destructive.

From the tool's definition The tool 'lever_archive_candidate' performs an action that 'Archive a candidate with a specific reason.' Archiving is a state-change operation that marks a candidate record as archived, which is a reversible modification (candidates can typically be…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lever_archive_candidate Rate-limited

lever_archive_candidate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lever_archive_candidate": {
      "limits": [
        {
          "counter": "lever_archive_candidate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lever ATS MCP Server, so you can run agents against it safely.

FAQ

Questions about lever_archive_candidate

What does the lever_archive_candidate tool do? +

Archive a candidate with a specific reason. It is categorised as a Write tool in the Lever ATS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lever_archive_candidate? +

Register the Lever ATS MCP Server MCP server in PolicyLayer and add a rule for lever_archive_candidate: 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 Lever ATS MCP Server. Nothing to install.

What risk level is lever_archive_candidate? +

lever_archive_candidate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lever_archive_candidate? +

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

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

lever_archive_candidate is provided by the Lever ATS MCP Server MCP server (the-sid-dani/lever-mcp-integration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.