Transfer a product from one location to another in your Grocy instance.
AI agents use transfer_product to commit financial operations through MCP Grocy API — usually the final step of a payment, billing, or trading workflow. A call moves real money.
transfer_product moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Documented attack patterns abuse exactly the kind of access transfer_product gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Grocy API, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer_product:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_product": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer_product is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer a product from one location to another in your Grocy instance. It is categorised as a Financial tool in the MCP Grocy API MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MCP Grocy API MCP server in PolicyLayer and add a rule for transfer_product: 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 MCP Grocy API. Nothing to install.
transfer_product 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 transfer_product 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 transfer_product. 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.
transfer_product is provided by the MCP Grocy API MCP server (saya6k/mcp-grocy-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 37 MCP Grocy API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
37 MCP Grocy API tools catalogued and risk-classified — across an index of 42,500+ MCP servers.