Get the signed-in user / guest Kismet account profile, identity, preferences, and account-level signals. Returns the currently authenticated user's (the logged-in guest's) Kismet profile: identity (first name, language, locale), contact-channel status (whether an email / phone is on file and veri...
Part of the Mcp Server server.
Free to start. No card required.
AI agents call get_guest_profile to retrieve information from Mcp Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_guest_profile only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_guest_profile": {}
}
}See the full Mcp Server policy for all 11 tools.
These attack patterns abuse exactly the kind of access get_guest_profile gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get the signed-in user / guest Kismet account profile, identity, preferences, and account-level signals. Returns the currently authenticated user's (the logged-in guest's) Kismet profile: identity (first name, language, locale), contact-channel status (whether an email / phone is on file and verified — never the raw values), communication preferences (channel preferences, marketing opt-in), account-level signals (saved payment method status, linked property managers and collections the user has transacted with, plus membership status — which collections the user is an Insider member of, unlocking member-only offers and drops), and a cross-collection activity summary (booking counts, last active, last booked across the Kismet network). Use this whenever the user wants to see their account, profile, or saved preferences, or whenever you need to personalize search results and recommendations for the signed-in user — common queries: "what does my profile look like", "who am I logged in as", "show my Kismet account", "check my preferences", "am I signed in", "personalize this for me". The response shape is forward-compatible — additional fields like stay history across rentals, current offers, and Kismet rewards wallet balance will appear here over time without changing the tool call signature. Returns an explicit anonymous state when no user is signed in. Anonymous browsing, search, and shortlisting are fully supported, so sign-in is not required for those flows. When auth_state is "anonymous", personal-account data (profile, stay history, bookings, preferences, saved payment, shortlist) is unavailable until the user signs in; the separate sign_in tool initiates the OAuth flow when the user wants to access it. This tool only READS the current auth state and never signs the user in.. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Server MCP server in PolicyLayer and add a rule for get_guest_profile: 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_guest_profile 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_guest_profile 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_guest_profile. 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_guest_profile 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.
Deterministic rules across all 11 Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.