retrieve_applicants

Retrieves an applicant.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=

SERVERWpm Mcp Server SOURCEwpm-mcp-server-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/wpm-mcp-server/retrieve-applicants.md

WHAT IT DOES

What retrieve_applicants does on Wpm Mcp Server

AI agents call retrieve_applicants to retrieve information from Wpm 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 retrieve_applicants is rated Low

The tool retrieves applicant data without side effects. It reads information about an applicant but does not create, modify, delete, or trigger financial operations. This is a classic Read operation with low severity due to its passive nature—misuse would involve accessing applicant data but not causing irreversible harm or financial impact.

From the tool's definition Tool name 'retrieve_applicants' indicates data retrieval. Description states 'Retrieves an applicant' with no mention of modification, deletion, or financial transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs retrieve_applicants safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wpm Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For retrieve_applicants, this is the rule to start with:

retrieve_applicants Allowed

retrieve_applicants 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": {
    "retrieve_applicants": {}
  }
}

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

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

FAQ

Questions about retrieve_applicants

What does the retrieve_applicants tool do? +

Retrieves an applicant.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Read tool in the Wpm Mcp Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retrieve_applicants? +

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

What risk level is retrieve_applicants? +

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

Can I rate-limit retrieve_applicants? +

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

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

retrieve_applicants is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wpm Mcp Server, and thousands of servers like it.

This server

All 420 Wpm Mcp Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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