Returns collection-level content for a VRM. Sections: "about" (collection info), "reviews" (guest reviews with ratings). Use for guest questions about the company, area, or review quality.
AI agents call get_vrm_content to retrieve information from Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max items for reviews. Default 10. |
offset | number | — | Pagination offset |
section | string | Yes | Content section |
collections | array | — | Collection slug(s) — each a `collection_id` from list_collections. For search_properties and discover_collections: OMIT to span the whole network, pass one to s |
Parameters from the server's own tool schema.
This is a read-only tool that retrieves and displays static content (collection information and guest reviews) for informational purposes. It has no side effects, cannot modify data, and poses minimal security risk. The narrow scope of returned data (collection metadata and reviews) and read-only nature justify low severity.
From the tool's definition Tool returns collection-level content including 'about' information and 'reviews' with ratings. Verbs indicate retrieval: 'Returns', 'Use for guest questions'. No mutation, deletion, or external execution described.
Attacks that exploit this kind of access
Returns collection-level content for a VRM. Sections: "about" (collection info), "reviews" (guest reviews with ratings). Use for guest questions about the company, area, or review quality. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_vrm_content accepts 4 parameters: limit, offset, section, collections. Required: section. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for get_vrm_content: 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 Mcp Server. Nothing to install.
get_vrm_content 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_vrm_content 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_vrm_content. 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_vrm_content is provided by the Mcp Server MCP server (https://mcp.kismet.travel/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 →