hires_upload_candidate_file
Upload a file for a candidate using a base64 payload. Used for resume ingestion, portfolio uploads, and document attachment.
This record as markdown: /tools/100hires-mcp-server/hires-upload-candidate-file.md
What hires_upload_candidate_file does on 100Hires MCP Server
AI agents use hires_upload_candidate_file to create or update resources in 100Hires MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 100Hires MCP Server environment.
Why hires_upload_candidate_file is rated Medium
File upload is a write operation that creates new data objects in the candidate record. Severity is medium because malicious file uploads could introduce malware or fraudulent documents into hiring records, affecting recruitment workflows and compliance. However, the operation is reversible (files can be deleted), so it does not rise to Destructive.
From the tool's definition Tool name and description explicitly state 'Upload a file for a candidate' — this creates or modifies data (resume, portfolio, document attachment) in the ATS system. The base64 payload mechanism confirms file creation/storage.
Attacks that exploit this kind of access
The rule that runs hires_upload_candidate_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 100Hires MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hires_upload_candidate_file, this is the rule to start with:
hires_upload_candidate_file 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 100Hires MCP Server, apply this rule, and every hires_upload_candidate_file call is checked against it from then on.
Questions about hires_upload_candidate_file
Upload a file for a candidate using a base64 payload. Used for resume ingestion, portfolio uploads, and document attachment. It is categorised as a Write tool in the 100Hires MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 100Hires MCP Server MCP server in PolicyLayer and add a rule for hires_upload_candidate_file: 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 100Hires MCP Server. Nothing to install.
hires_upload_candidate_file 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 hires_upload_candidate_file 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 hires_upload_candidate_file. 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.
hires_upload_candidate_file is provided by the 100Hires MCP Server MCP server (100hires/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 100Hires MCP Server, and thousands of servers like it.
This server
Across the catalogue