snow_update_ux_app_config_landing_page
Update App Configuration with Landing Page Route - Sets the default landing page for the workspace.
This record as markdown: /tools/serac/snow-update-ux-app-config-landing-page.md
What snow_update_ux_app_config_landing_page does on Serac
AI agents use snow_update_ux_app_config_landing_page to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_update_ux_app_config_landing_page is rated Medium
This tool modifies application configuration (landing page route) rather than creating/deleting core data. The change is reversible — the landing page can be updated again to a different value or reset. While it affects user experience and workspace behavior, it does not execute arbitrary code, delete data, or move money. It fits the Write category: creates or modifies data reversibly.
From the tool's definition Tool name contains 'update' and description states 'Sets the default landing page' — a configuration modification that creates or changes workspace settings reversibly.
Attacks that exploit this kind of access
The rule that runs snow_update_ux_app_config_landing_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_update_ux_app_config_landing_page, this is the rule to start with:
snow_update_ux_app_config_landing_page stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_update_ux_app_config_landing_page call is checked against it from then on.
Questions about snow_update_ux_app_config_landing_page
Update App Configuration with Landing Page Route - Sets the default landing page for the workspace. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_update_ux_app_config_landing_page: 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 Serac. Nothing to install.
snow_update_ux_app_config_landing_page 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 snow_update_ux_app_config_landing_page 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 snow_update_ux_app_config_landing_page. 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.
snow_update_ux_app_config_landing_page is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue