[FacturaHub] Close the current cash register session. Provide the actual cash count for reconciliation.
AI agents use close_register to commit financial operations through FacturaHub MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Closing a cash register session is a financial operation that finalizes and commits a POS session, reconciling cash counts. This is a financial transaction boundary operation that affects financial records and cannot be trivially undone, making it Financial category with high severity since misuse could corrupt cash reconciliation records.
From the tool's definition Close the current cash register session. Provide the actual cash count for reconciliation.
Attacks that exploit this kind of access
[FacturaHub] Close the current cash register session. Provide the actual cash count for reconciliation. It is categorised as a Financial tool in the FacturaHub MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the FacturaHub MCP Server MCP server in PolicyLayer and add a rule for close_register: 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 FacturaHub MCP Server. Nothing to install.
close_register is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the close_register 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 close_register. 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.
close_register is provided by the FacturaHub MCP Server MCP server (santy1422/facturahub-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 →