AI agents use create_reservation to create or update resources in Boma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Boma MCP environment.
This tool creates new reservation records in the Boma platform. Creation of reversible bookings falls squarely into the Write category. Severity is low because: (1) room reservation conflicts are easily remedied by modifying or deleting reservations, (2) no financial transactions are involved, (3) no code execution or system-level operations occur, and (4) impact is limited to calendar/scheduling data with minimal…
From the tool's definition Tool description states 'Create a new room reservation' — the verb 'create' indicates creation of new data without irreversibility or financial obligation.
Attacks that exploit this kind of access
Create a new room reservation. Available rooms: Big Mike, Gran Enana, Lakatán, Dacca, Cavendish, Dominico. Time slots are in 30-minute intervals. It is categorised as a Write tool in the Boma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Boma MCP server in PolicyLayer and add a rule for create_reservation: 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 Boma MCP. Nothing to install.
create_reservation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_reservation 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.
Set action: deny in the PolicyLayer policy for create_reservation. 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.
create_reservation is provided by the Boma MCP server (nicolasvegam/boma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →