manage_returns · Pancake POS MCP: Risk & Policy

WHAT IT DOES

What manage_returns does on Pancake POS MCP

AI agents use manage_returns 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_returns needs a policy

This tool creates and updates return/exchange records and processes refunds in a POS system, which are reversible write operations. Although it includes a delete action, the context indicates it manages business transactions (returns/exchanges) rather than performing hard deletion of core data.

From the tool's definition Tool description states 'Manage order returns and exchanges' with actions including 'create, update, delete'. While delete is present, the primary function is managing returns/exchanges (reversible business operations), not irreversible data destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_returns Rate-limited

manage_returns 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_returns": {
      "limits": [
        {
          "counter": "manage_returns_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_returns

What does the manage_returns tool do? +

Manage order returns and exchanges in Pancake POS. Actions: list, get, create, update, delete. Supports exchange flow (return + new items). 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_returns? +

Register the Pancake POS MCP server in PolicyLayer and add a rule for manage_returns: 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_returns? +

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

Can I rate-limit manage_returns? +

Yes. Add a rate_limit block to the manage_returns 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_returns completely? +

Set action: deny in the PolicyLayer policy for manage_returns. 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_returns? +

manage_returns 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.