Present a curated set of specific properties as an interactive visual carousel. Pass propertySlugs in your chosen order, plus the collection_id(s) those properties belong to in collections — you get each candidate's collectionSlug from search_properties. The picks MAY span multiple managers: pass...
Part of the Mcp Server server.
Free to start. No card required.
AI agents invoke build_property_carousel 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.
build_property_carousel 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": {
"build_property_carousel": {
"limits": [
{
"counter": "build_property_carousel_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 build_property_carousel 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.
Present a curated set of specific properties as an interactive visual carousel. Pass propertySlugs in your chosen order, plus the collection_id(s) those properties belong to in collections — you get each candidate's collectionSlug from search_properties. The picks MAY span multiple managers: pass ALL their collection_ids and the carousel renders them together with manager filter cards. Never fall back to a plain text list for a cross-manager set — this tool handles it. Call AFTER search_properties.. 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 build_property_carousel: 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.
build_property_carousel 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 build_property_carousel 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 build_property_carousel. 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.
build_property_carousel 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.