Trigger the Kismet OAuth sign-in flow for the current guest. Call this whenever the user explicitly asks to sign in, log in, authenticate, or connect their Kismet account — common queries: "sign me in", "log me in", "log me into Kismet", "sign me into Kismet", "connect my Kismet account", "authen...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Mcp Server server.
Free to start. No card required.
AI agents invoke sign_in to trigger processes or run actions in Mcp Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
sign_in can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"sign_in": {
"limits": [
{
"counter": "sign_in_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Mcp Server policy for all 11 tools.
These attack patterns abuse exactly the kind of access sign_in gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Trigger the Kismet OAuth sign-in flow for the current guest. Call this whenever the user explicitly asks to sign in, log in, authenticate, or connect their Kismet account — common queries: "sign me in", "log me in", "log me into Kismet", "sign me into Kismet", "connect my Kismet account", "authenticate me", "I want to log in". The host will open its OAuth WebView and run the standard PKCE handshake; after successful authentication this tool returns a confirmation snapshot of the signed-in identity (display name, email — when verified) and every subsequent tool call (get_guest_profile, get_shortlist, shortlist_property, etc.) will see the authenticated guest. Do NOT call this tool unless the user explicitly asked to sign in — anonymous browsing, search, and shortlisting all work fully without sign-in. After a successful sign-in, call get_guest_profile to surface the guest's full Kismet profile to the conversation.. It is categorised as a Execute tool in the Mcp Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Server MCP server in PolicyLayer and add a rule for sign_in: 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.
sign_in is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sign_in 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 sign_in. 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.
sign_in 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.