refresh_token · Restaurant Reservation MCP Server MCP

WHAT IT DOES

What refresh_token does on Restaurant Reservation MCP Server

AI agents invoke refresh_token to trigger actions in Restaurant Reservation MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why refresh_token needs a policy

This tool triggers an external authentication operation — it uses stored credentials to call an identity/auth service and obtain a new token. It doesn't simply read data, nor does it write user-visible data; it executes an auth flow with side effects (issuing a new token, potentially invalidating the old one).

From the tool's definition 'Manually refresh authentication token using stored login credentials'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_token Rate-limited

refresh_token stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_token": {
      "limits": [
        {
          "counter": "refresh_token_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 Reservation MCP Server, so you can run agents against it safely.

FAQ

Questions about refresh_token

What does the refresh_token tool do? +

Manually refresh authentication token using stored login credentials. It is categorised as a Execute tool in the Restaurant Reservation MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on refresh_token? +

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

What risk level is refresh_token? +

refresh_token is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit refresh_token? +

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

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

refresh_token is provided by the Restaurant Reservation MCP Server MCP server (jrklein343-svg/restaurant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.