Update an existing bill in Sanka. To attach a supplier invoice PDF, upload the original file first with upload_bill_attachment for already available base64 payloads, or with start_bill_attachment_upload plus append_bill_attachment_upload_chunk until done and finish_bill_attachment_upload for clie...
AI agents use update_bill 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.
This tool modifies existing billing records reversibly through an update operation. It is categorized as Write rather than Destructive because updates are non-destructive and reversible. Severity is medium because bill modifications could affect financial records and business operations, but the actual financial impact depends on what values are changed and requires an authorized user to invoke the operation.
From the tool's definition Tool name 'update_bill' and description 'Update an existing bill in Sanka' indicates modification of existing bill records.
Attacks that exploit this kind of access
Update an existing bill in Sanka. To attach a supplier invoice PDF, upload the original file first with upload_bill_attachment for already available base64 payloads, or with start_bill_attachment_upload plus append_bill_attachment_upload_chunk until done and finish_bill_attachment_upload for client-local PDFs or unreliable large payloads. Pass returned file_id values in. 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 update_bill: 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.
update_bill 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 update_bill 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 update_bill. 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.
update_bill 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 →