update_work_history · CATS MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_work_history does on CATS MCP Server

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

WHY IT NEEDS A POLICY

Why update_work_history needs a policy

The tool name clearly indicates a write operation that modifies candidate work history data within an applicant tracking system. This is reversible (typical of Write category) and contextually part of candidate record management.

From the tool's definition Tool name 'update_work_history' indicates modification of candidate work history records. Part of CATS recruiting/applicant tracking system toolset focused on candidate management. Description is empty, limiting direct confirmation of scope.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_work_history Rate-limited

update_work_history 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_work_history": {
      "limits": [
        {
          "counter": "update_work_history_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 CATS MCP Server, so you can run agents against it safely.

FAQ

Questions about update_work_history

What does the update_work_history tool do? +

update_work_history. It is categorised as a Write tool in the CATS 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_work_history? +

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

What risk level is update_work_history? +

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

Can I rate-limit update_work_history? +

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

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

update_work_history is provided by the CATS MCP Server MCP server (vanman2024/cats-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.