Load READ-ONLY context from a Kismet guest token — e.g. a "continue in your AI assistant" link a property manager handed the guest. Returns the manager, any current offer, and the draft/considered itinerary the token carries, so you can have an informed conversation. This is CONTEXT ONLY: it gran...
Risk signalsHandles credentials or secrets (token)
Part of the Mcp Server server.
Free to start. No card required.
AI agents use use_guest_token to create or modify resources in Mcp Server. 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 use_guest_token repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"use_guest_token": {
"limits": [
{
"counter": "use_guest_token_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Mcp Server policy for all 11 tools.
These attack patterns abuse exactly the kind of access use_guest_token gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Load READ-ONLY context from a Kismet guest token — e.g. a "continue in your AI assistant" link a property manager handed the guest. Returns the manager, any current offer, and the draft/considered itinerary the token carries, so you can have an informed conversation. This is CONTEXT ONLY: it grants NO account access and is never required for browsing. To actually claim an offer, save itinerary changes, message the manager, or book, the guest must sign in — call sign_in (the standard OAuth flow). Call this when the user pastes or references a Kismet guest/booking token or such a handoff link. An unrecognized or expired token returns a clean invalid state (never an error) — then offer to sign them in.. It is categorised as a Write tool in the Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Server MCP server in PolicyLayer and add a rule for use_guest_token: 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.
use_guest_token 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 use_guest_token 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 use_guest_token. 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.
use_guest_token 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.