AI agents call get_reservations_by_user to retrieve information from Boma MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves (queries) reservation data for a specific user with no side effects. It does not create, modify, delete, or execute operations. The default scoping to the authenticated user reduces the severity of potential over-exposure. This is a straightforward Read operation within a meeting room reservation management system.
From the tool's definition Tool name 'get_reservations_by_user' and description 'Get all reservations for a specific user' indicate a query operation that retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
Get all reservations for a specific user. Defaults to the authenticated user. It is categorised as a Read tool in the Boma MCP MCP Server, which means it retrieves data without modifying state.
Register the Boma MCP server in PolicyLayer and add a rule for get_reservations_by_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 Boma MCP. Nothing to install.
get_reservations_by_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_reservations_by_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.
Set action: deny in the PolicyLayer policy for get_reservations_by_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.
get_reservations_by_user 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 →