Upload a file to Passgage using presigned URL
AI agents use passgage_upload_file 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.
Uploading a file creates or modifies data in Passgage (a workforce management system handling HR and personnel data). This is a Write operation because it is reversible — uploaded files can typically be deleted or replaced. It is not Destructive because the action is not irreversible.
From the tool's definition Tool name 'passgage_upload_file' and description 'Upload a file to Passgage using presigned URL' indicate file creation/modification in the workforce management system.
Attacks that exploit this kind of access
Upload a file to Passgage using presigned URL. 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.
Register the Passgage MCP Server MCP server in PolicyLayer and add a rule for passgage_upload_file: 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.
passgage_upload_file 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 passgage_upload_file 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 passgage_upload_file. 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.
passgage_upload_file 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →