manage_transfers · Pancake POS MCP: Risk & Policy

WHAT IT DOES

What manage_transfers does on Pancake POS MCP

AI agents use manage_transfers to create or update resources in Pancake POS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pancake POS MCP environment.

WHY IT NEEDS A POLICY

Why manage_transfers needs a policy

This tool modifies inventory data through warehouse transfers (create, update) and can remove transfer records (delete). However, in a POS context, deleting a transfer record is typically reversible administrative action on metadata rather than irreversible destruction of physical inventory. The primary risk is incorrect transfers misallocating stock, which is a Write-level concern.

From the tool's definition Tool description states it can 'create, update, delete' warehouse transfers. While delete is present, the context of 'stock transfers' suggests reversible inventory management operations rather than permanent data destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_transfers Rate-limited

manage_transfers stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_transfers": {
      "limits": [
        {
          "counter": "manage_transfers_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pancake POS MCP, so you can run agents against it safely.

FAQ

Questions about manage_transfers

What does the manage_transfers tool do? +

Manage warehouse-to-warehouse stock transfers in Pancake POS. Actions: list, get, create, update, delete. It is categorised as a Write tool in the Pancake POS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_transfers? +

Register the Pancake POS MCP server in PolicyLayer and add a rule for manage_transfers: 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 Pancake POS MCP. Nothing to install.

What risk level is manage_transfers? +

manage_transfers is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_transfers? +

Yes. Add a rate_limit block to the manage_transfers 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.

How do I block manage_transfers completely? +

Set action: deny in the PolicyLayer policy for manage_transfers. 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.

What MCP server provides manage_transfers? +

manage_transfers is provided by the Pancake POS MCP server (svn4pro/pancake-pos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.