upload_purchase_order_attachment
Upload a purchase order attachment to Sanka from an already available base64 payload. Prefer this direct upload when the client can pass content_base64 reliably. For client-local PDFs or payloads that are too large or unreliable to pass as one content_base64 string, use start_purchase_order_attac...
This record as markdown: /tools/sankahq-sanka-mcp/upload-purchase-order-attachment.md
What upload_purchase_order_attachment does on Sanka MCP Server
AI agents use upload_purchase_order_attachment to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
Why upload_purchase_order_attachment is rated Medium
This tool creates or stores new attachment data in the system, making it a Write operation. While it modifies business documents (purchase orders), the action is reversible—attachments can be removed or replaced. Severity is medium because incorrect file uploads in a financial/procurement context could cause operational issues, but the tool itself doesn't move money or irreversibly delete data.
From the tool's definition Tool description states 'Upload a purchase order attachment' and 'Use the returned file_id in create_purchase_order or update_purchase_order', indicating it creates/modifies data in Sanka's system.
Attacks that exploit this kind of access
The rule that runs upload_purchase_order_attachment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_purchase_order_attachment, this is the rule to start with:
upload_purchase_order_attachment 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 Sanka MCP Server, apply this rule, and every upload_purchase_order_attachment call is checked against it from then on.
Questions about upload_purchase_order_attachment
Upload a purchase order attachment to Sanka from an already available base64 payload. Prefer this direct upload when the client can pass content_base64 reliably. For client-local PDFs or payloads that are too large or unreliable to pass as one content_base64 string, use start_purchase_order_attachment_upload, append_purchase_order_attachment_upload_chunk until done, then finish_purchase_order_attachment_upload. Use the returned file_id in create_purchase_order or update_purchase_order. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for upload_purchase_order_attachment: 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 Sanka MCP Server. Nothing to install.
upload_purchase_order_attachment 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 upload_purchase_order_attachment 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 upload_purchase_order_attachment. 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.
upload_purchase_order_attachment is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue