upload_resume

Upload/replace the candidate

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/upload-resume.md

WHAT IT DOES

What upload_resume does on ProAgentStore

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

RISK

Why upload_resume is rated Medium

This tool modifies candidate profile information by uploading or replacing a resume. While it affects recruitment data, it is reversible (the previous resume could theoretically be restored), making it Write rather than Destructive.

From the tool's definition Tool description states 'Upload/replace the candidate', indicating it creates or modifies candidate resume data. The 'replace' verb suggests it can overwrite existing data reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs upload_resume safely

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

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.

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

FAQ

Questions about upload_resume

What does the upload_resume tool do? +

Upload/replace the candidate. It is categorised as a Write tool in the ProAgentStore 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 ProAgentStore 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 ProAgentStore. 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 ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

resume_renders on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →