Medium Risk

rigshare_create_booking

REQUIRES API KEY (bookings:write scope). Creates a new RIGShare booking for the authenticated user. Server computes all prices from the equipment's canonical rates — client-side price hints are ignored. Enforces identity verification, security deposit hold, and a daily/monthly budget cap configur...

Part of the Rigshare MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

rigshare-mcp Write

AI agents use rigshare_create_booking to create or modify resources in Rigshare. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call rigshare_create_booking repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Rigshare.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-rper2001-rigshare.yaml
tools:
  rigshare_create_booking:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Rigshare policy for all 7 tools.

Tool Name rigshare_create_booking
Category Write
MCP Server Rigshare MCP Server
Risk Level Medium

Agents calling write-class tools like rigshare_create_booking have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the rigshare_create_booking tool do? +

REQUIRES API KEY (bookings:write scope). Creates a new RIGShare booking for the authenticated user. Server computes all prices from the equipment's canonical rates — client-side price hints are ignored. Enforces identity verification, security deposit hold, and a daily/monthly budget cap configured on the API key. Returns confirmation code + booking ID on success. Use rigshare_list_my_bookings to check status afterwards.. It is categorised as a Write tool in the Rigshare MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rigshare_create_booking? +

Add a rule in your Intercept YAML policy under the tools section for rigshare_create_booking. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rigshare MCP server.

What risk level is rigshare_create_booking? +

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

Can I rate-limit rigshare_create_booking? +

Yes. Add a rate_limit block to the rigshare_create_booking rule in your Intercept 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 rigshare_create_booking completely? +

Set action: deny in the Intercept policy for rigshare_create_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 rigshare_create_booking? +

rigshare_create_booking is provided by the Rigshare MCP server (rigshare-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.