batch_assign_pass_logistics
Assign transport logistics or priority pass tiers in bulk to a group of passengers/holders and emit real-time UI state mutations to the Partner Hub.
This record as markdown: /tools/81pass-mcp-server/batch-assign-pass-logistics.md
What batch_assign_pass_logistics does on 81pass
AI agents use batch_assign_pass_logistics to create or update resources in 81pass, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 81pass environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
org_id | string | Yes | Organization ID (e.g. hb_b2b) |
agent_id | string | — | Identifier of the calling BYOA agent |
assignee_type | string | Yes | Transport or priority pass tier to assign |
passenger_ids | array | Yes | Array of passenger/credential IDs to process in bulk |
Parameters from the server's own tool schema.
Why batch_assign_pass_logistics is rated Medium
An AI agent can call batch_assign_pass_logistics faster than any human can review: one bad instruction and it creates or modifies resources in 81pass by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_assign_pass_logistics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 81pass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_assign_pass_logistics, this is the rule to start with:
batch_assign_pass_logistics 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 81pass, apply this rule, and every batch_assign_pass_logistics call is checked against it from then on.
Questions about batch_assign_pass_logistics
Assign transport logistics or priority pass tiers in bulk to a group of passengers/holders and emit real-time UI state mutations to the Partner Hub. It is categorised as a Write tool in the 81pass MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
batch_assign_pass_logistics accepts 4 parameters: org_id, agent_id, assignee_type, passenger_ids. Required: org_id, assignee_type, passenger_ids. The full parameter table on this page comes from the server's own tool schema.
Register the 81pass MCP server in PolicyLayer and add a rule for batch_assign_pass_logistics: 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 81pass. Nothing to install.
batch_assign_pass_logistics is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the batch_assign_pass_logistics 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.
Set action: deny in the PolicyLayer policy for batch_assign_pass_logistics. 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.
batch_assign_pass_logistics is provided by the 81pass MCP server (@81pass/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 81pass, and thousands of servers like it.
This server
Across the catalogue