update_resume_data · Resume Forge MCP: Risk & Policy

WHAT IT DOES

What update_resume_data does on Resume Forge MCP

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

WHY IT NEEDS A POLICY

Why update_resume_data needs a policy

This tool creates or modifies resume data reversibly, fitting the Write category. Severity is high because unauthorized modifications to a user's resume could cause reputational damage, job application rejection, or identity-related harm. Confidence is 0.85 due to the empty description; a filled description would increase certainty to 0.95+.

From the tool's definition Tool name 'update_resume_data' indicates modification of stored resume data. The empty description prevents direct confirmation, but the 'update_' prefix and sibling tools like 'get_resume_data', 'import_resume', and 'generate_resume' establish this as a data…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_resume_data Rate-limited

update_resume_data 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": {
    "update_resume_data": {
      "limits": [
        {
          "counter": "update_resume_data_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 Resume Forge MCP, so you can run agents against it safely.

FAQ

Questions about update_resume_data

What does the update_resume_data tool do? +

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

How do I enforce a policy on update_resume_data? +

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

What risk level is update_resume_data? +

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

Can I rate-limit update_resume_data? +

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

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

update_resume_data is provided by the Resume Forge MCP server (jitendrasinghsankhwar/resume-forge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.