create_upload_request_files
Uploading a file requires making two API requests. Each step is outlined below.\r\n\r\n\r\n<strong>Step 1 - Save file metadata</strong>\r\n\r\nThe first step in the file upload process is to submit the file metadata to
This record as markdown: /tools/wpm-mcp-server/create-upload-request-files.md
What create_upload_request_files does on Wpm Mcp Server
AI agents use create_upload_request_files to create or update resources in Wpm Mcp Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wpm Mcp Server environment.
Why create_upload_request_files is rated Medium
This tool creates or uploads files, which is a reversible write operation. It modifies system state by adding new file resources, but the action is not destructive (files can be deleted/replaced) and does not involve financial transactions or direct code execution.
From the tool's definition Tool name contains 'create' and description explicitly describes 'file upload process' and 'Save file metadata' which are write operations that create new file resources in the system.
Attacks that exploit this kind of access
The rule that runs create_upload_request_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wpm Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_upload_request_files, this is the rule to start with:
create_upload_request_files 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 Wpm Mcp Server, apply this rule, and every create_upload_request_files call is checked against it from then on.
Questions about create_upload_request_files
Uploading a file requires making two API requests. Each step is outlined below.\r\n\r\n\r\n<strong>Step 1 - Save file metadata</strong>\r\n\r\nThe first step in the file upload process is to submit the file metadata to. It is categorised as a Write tool in the Wpm Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for create_upload_request_files: 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 Wpm Mcp Server. Nothing to install.
create_upload_request_files 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 create_upload_request_files 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 create_upload_request_files. 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.
create_upload_request_files is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wpm Mcp Server, and thousands of servers like it.
This server
Across the catalogue