customer_login · Restaurant Backend MCP Server MCP

WHAT IT DOES

What customer_login does on Restaurant Backend MCP Server

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

WHY IT NEEDS A POLICY

Why customer_login needs a policy

Login operations create or establish user sessions, which are reversible modifications to system state (sessions can be terminated). While authentication touches sensitive data, it is a standard Write operation rather than Read (logs in rather than retrieves), Execute (doesn't run arbitrary code), or Destructive (reversible).

From the tool's definition Tool named 'customer_login' with empty description. Based on name and context of a restaurant backend system, this tool creates or modifies session/authentication state for customers.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

customer_login Rate-limited

customer_login 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": {
    "customer_login": {
      "limits": [
        {
          "counter": "customer_login_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 Restaurant Backend MCP Server, so you can run agents against it safely.

FAQ

Questions about customer_login

What does the customer_login tool do? +

customer_login. It is categorised as a Write tool in the Restaurant Backend MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on customer_login? +

Register the Restaurant Backend MCP Server MCP server in PolicyLayer and add a rule for customer_login: 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 Restaurant Backend MCP Server. Nothing to install.

What risk level is customer_login? +

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

Can I rate-limit customer_login? +

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

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

customer_login is provided by the Restaurant Backend MCP Server MCP server (pasanis/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.