Update an existing purchase invoice
AI agents use siigo_update_purchase to create or update resources in Siigo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Siigo MCP Server environment.
This tool modifies financial records (purchase invoices) in a live accounting system. While categorized as Write rather than Destructive because updates are typically reversible, the high severity reflects the critical nature of purchase data in financial accounting.
From the tool's definition Tool name is siigo_update_purchase and description states 'Update an existing purchase invoice'. The verb 'update' indicates modification of existing data in the accounting system.
Attacks that exploit this kind of access
Update an existing purchase invoice. It is categorised as a Write tool in the Siigo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Siigo MCP Server MCP server in PolicyLayer and add a rule for siigo_update_purchase: 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 Siigo MCP Server. Nothing to install.
siigo_update_purchase 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 siigo_update_purchase 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 siigo_update_purchase. 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.
siigo_update_purchase is provided by the Siigo MCP Server MCP server (jdlar1/siigo-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 →