login_user · Petstore MCP Server MCP: Risk & Policy

WHAT IT DOES

What login_user does on Petstore MCP Server

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

WHY IT NEEDS A POLICY

Why login_user needs a policy

An AI agent can call login_user faster than any human can review — one bad instruction and it creates or modifies resources in Petstore MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

login_user Rate-limited

login_user 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": {
    "login_user": {
      "limits": [
        {
          "counter": "login_user_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 Petstore MCP Server, so you can run agents against it safely.

FAQ

Questions about login_user

What does the login_user tool do? +

Log user into the system. It is categorised as a Write tool in the Petstore 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 login_user? +

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

What risk level is login_user? +

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

Can I rate-limit login_user? +

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

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

login_user is provided by the Petstore MCP Server MCP server (raghavendraprakash/mcpforrestapis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.