request_booking · Rover MCP Server MCP: Risk & Policy

WHAT IT DOES

What request_booking does on Rover MCP Server

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

WHY IT NEEDS A POLICY

Why request_booking needs a policy

This tool creates a new booking request which is a data modification operation. It is reversible (bookings can be cancelled or requests declined), so it qualifies as Write rather than Destructive. The severity is medium because misuse could result in unwanted financial commitments or service obligations, though the booking is still a request pending sitter acceptance rather than a confirmed transaction.

From the tool's definition The tool name 'request_booking' combined with the description 'Send a booking request to a sitter' indicates creation of a new booking record in the Rover marketplace system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

request_booking Rate-limited

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

FAQ

Questions about request_booking

What does the request_booking tool do? +

Send a booking request to a sitter. Requires being logged in. It is categorised as a Write tool in the Rover 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 request_booking? +

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

What risk level is request_booking? +

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

Can I rate-limit request_booking? +

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

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

request_booking is provided by the Rover MCP Server MCP server (markswendsen-code/mcp-rover). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.