generate_resume · LinkedIn MCP Pro Max MCP: Risk & Policy

WHAT IT DOES

What generate_resume does on LinkedIn MCP Pro Max

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

WHY IT NEEDS A POLICY

Why generate_resume needs a policy

This tool creates a new resume document based on LinkedIn profile data. While the resume generation itself does not modify the LinkedIn profile or other persistent data stores, it does produce a new written artifact (the resume). This falls under Write category (creates or modifies data reversibly) rather than Read (which would only retrieve existing data).

From the tool's definition Tool description states 'Generate a professional resume from a LinkedIn profile using AI enhancement.' The verb 'Generate' indicates creation of a new document artifact. The tool produces and outputs a resume document, which is a form of data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_resume Rate-limited

generate_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": {
    "generate_resume": {
      "limits": [
        {
          "counter": "generate_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 LinkedIn MCP Pro Max, so you can run agents against it safely.

FAQ

Questions about generate_resume

What does the generate_resume tool do? +

Generate a professional resume from a LinkedIn profile using AI enhancement. It is categorised as a Write tool in the LinkedIn MCP Pro Max MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_resume? +

Register the LinkedIn MCP Pro Max MCP server in PolicyLayer and add a rule for generate_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 LinkedIn MCP Pro Max. Nothing to install.

What risk level is generate_resume? +

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

Can I rate-limit generate_resume? +

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

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

generate_resume is provided by the LinkedIn MCP Pro Max MCP server (mdnaimul22/linkedin-mcp-pro-max). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.