update_open_to_work · LinkedIn Profile MCP Server MCP

WHAT IT DOES

What update_open_to_work does on LinkedIn Profile MCP Server

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

WHY IT NEEDS A POLICY

Why update_open_to_work needs a policy

This tool modifies user profile visibility and job search status on LinkedIn, which is a reversible state change. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger external operations unpredictably (Execute).

From the tool's definition Tool name 'update_open_to_work' and description 'Update Open to Work status' directly indicate modification of profile state. This creates/modifies LinkedIn profile data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_open_to_work Rate-limited

update_open_to_work 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_open_to_work": {
      "limits": [
        {
          "counter": "update_open_to_work_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 Profile MCP Server, so you can run agents against it safely.

FAQ

Questions about update_open_to_work

What does the update_open_to_work tool do? +

Update Open to Work status. It is categorised as a Write tool in the LinkedIn Profile MCP Server 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_open_to_work? +

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

What risk level is update_open_to_work? +

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

Can I rate-limit update_open_to_work? +

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

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

update_open_to_work is provided by the LinkedIn Profile MCP Server MCP server (thejosem4/linkedin-profile-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.