passgage_track_entrance · Passgage MCP Server MCP

WHAT IT DOES

What passgage_track_entrance does on Passgage MCP Server

AI agents use passgage_track_entrance 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_track_entrance needs a policy

This tool creates or records new time tracking events, which is reversible data modification. It does not delete, execute arbitrary commands, or move money. The medium severity reflects that misuse could distort time records and affect payroll calculations or attendance reporting, but the impact is limited to a single user's time entry and can typically be corrected by authorized personnel.

From the tool's definition Tool name 'passgage_track_entrance' and description 'Record an entrance/exit event for a user' indicate creation of time tracking records. This modifies workforce management data by logging entrance/exit events.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

passgage_track_entrance Rate-limited

passgage_track_entrance 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_track_entrance": {
      "limits": [
        {
          "counter": "passgage_track_entrance_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_track_entrance

What does the passgage_track_entrance tool do? +

Record an entrance/exit event for a user. 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_track_entrance? +

Register the Passgage MCP Server MCP server in PolicyLayer and add a rule for passgage_track_entrance: 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_track_entrance? +

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

Can I rate-limit passgage_track_entrance? +

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

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

passgage_track_entrance 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.