Get list of purchase invoices (facturas de compra) from Siigo
AI agents call siigo_get_purchases to retrieve information from Siigo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists purchase invoice data from the Siigo accounting system without modifying, deleting, or executing any operations. It is a straightforward data query operation that falls squarely within the Read category. The low severity reflects that unauthorized access to purchase records, while sensitive, does not permit an AI agent to modify financial state or trigger financial transactions.
From the tool's definition Tool name 'siigo_get_purchases' with description 'Get list of purchase invoices' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get list of purchase invoices (facturas de compra) from Siigo. It is categorised as a Read tool in the Siigo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Siigo MCP Server MCP server in PolicyLayer and add a rule for siigo_get_purchases: 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_get_purchases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the siigo_get_purchases 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_get_purchases. 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_get_purchases 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 →