passgage_assign_user_to_shift · Passgage MCP Server MCP

WHAT IT DOES

What passgage_assign_user_to_shift does on Passgage MCP Server

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

WHY IT NEEDS A POLICY

Why passgage_assign_user_to_shift needs a policy

This tool creates or modifies shift assignments reversibly within a workforce management system. While it changes operational data (shift schedules), the change is not destructive and can typically be undone by reassigning or removing the user from the shift. It does not delete data, execute arbitrary code, or trigger financial transactions. It falls squarely in the Write category.

From the tool's definition Tool name is 'passgage_assign_user_to_shift' and description states it 'Assign a user to a specific shift'. This modifies workforce scheduling data by creating or updating a shift assignment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

passgage_assign_user_to_shift Rate-limited

passgage_assign_user_to_shift 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": {
    "passgage_assign_user_to_shift": {
      "limits": [
        {
          "counter": "passgage_assign_user_to_shift_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 Passgage MCP Server, so you can run agents against it safely.

FAQ

Questions about passgage_assign_user_to_shift

What does the passgage_assign_user_to_shift tool do? +

Assign a user to a specific shift. It is categorised as a Write tool in the Passgage 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 passgage_assign_user_to_shift? +

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

What risk level is passgage_assign_user_to_shift? +

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

Can I rate-limit passgage_assign_user_to_shift? +

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

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

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