Get all available archive reasons.
AI agents call lever_get_archive_reasons to retrieve information from Lever ATS 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 a static enumeration of archive reasons from the system. It performs a query-like operation to fetch configuration/reference data without creating, modifying, deleting, or executing any operations. This is a straightforward Read operation with minimal security risk.
From the tool's definition Tool name 'lever_get_archive_reasons' and description 'Get all available archive reasons' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all available archive reasons. It is categorised as a Read tool in the Lever ATS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lever ATS MCP Server MCP server in PolicyLayer and add a rule for lever_get_archive_reasons: 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.
lever_get_archive_reasons 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 lever_get_archive_reasons 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 lever_get_archive_reasons. 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.
lever_get_archive_reasons 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.
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 →