Creates an applicant.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=
AI agents use create_applicants to create or update resources in Wpm Mcp Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wpm Mcp Server environment.
This tool creates new applicant records, which is a Write operation (reversible data creation). Severity is medium because creating applicants could have downstream business implications (e.g., triggering automated processes, creating financial obligations through applications), but the action itself is not destructive or immediately financial.
From the tool's definition Tool name 'create_applicants' and description states 'Creates an applicant' - this is a create operation that adds new records to the system.
Attacks that exploit this kind of access
Creates an applicant.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Write tool in the Wpm Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for create_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.
create_applicants is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
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 →