upload_resume · Hiring MCP: Risk & Policy

WHAT IT DOES

What upload_resume does on Hiring

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

WHY IT NEEDS A POLICY

Why upload_resume needs a policy

This tool creates or modifies candidate data (resume upload) in the hiring system. It is reversible (can be updated or overwritten) and has no destructive or financial impact. Severity is medium because misuse could result in storing incorrect or malicious resume content associated with a candidate profile, potentially affecting hiring decisions, though the blast radius is limited to individual candidate records.

From the tool's definition Tool name 'upload_resume' and description 'Saves the candidate' indicate data creation/modification. The tool writes candidate resume data to storage (S3 mentioned in server description).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_resume Rate-limited

upload_resume 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": {
    "upload_resume": {
      "limits": [
        {
          "counter": "upload_resume_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 Hiring, so you can run agents against it safely.

FAQ

Questions about upload_resume

What does the upload_resume tool do? +

Saves the candidate. It is categorised as a Write tool in the Hiring MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_resume? +

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

What risk level is upload_resume? +

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

Can I rate-limit upload_resume? +

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

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

upload_resume is provided by the Hiring MCP server (meetvaghani12/hiring_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.