Upload an estimate 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_estimate_attachment_uploa...
AI agents use upload_estimate_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.
The tool creates or adds attachment metadata to estimate records in Sanka, which is a data modification operation. It does not delete, execute arbitrary code, or move money. While the upload process involves file handling, the primary action is writing attachment data to the system. This is reversible (attachments can be removed), making it Write rather than Destructive.
From the tool's definition Tool uploads and attaches files to estimate records ('Upload an estimate attachment', 'returned file_id in create_estimate or update_estimate'). This modifies estimate data by adding attachments—a reversible write operation.
Attacks that exploit this kind of access
Upload an estimate 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_estimate_attachment_upload, append_estimate_attachment_upload_chunk until done, then finish_estimate_attachment_upload. Use the returned file_id in create_estimate or update_estimate. 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_estimate_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_estimate_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_estimate_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_estimate_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_estimate_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.
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 →