High Risk →

navigate_ui

Look up how to perform an action in the Sidearm dashboard UI. Returns step-by-step instructions for dashboard operations such as uploading media, running searches, managing API keys, reviewing deals, buying credits, and more. Use this when the user asks how to do something in the dashboard or web...

Accepts freeform code/query input (query)

Part of the Sidearm MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

sidearmdrm/sidearm Execute Risk 4/5

AI agents invoke navigate_ui to trigger processes or run actions in Sidearm. 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.

navigate_ui can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept 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.

sidearmdrm-sidearm.yaml
tools:
  navigate_ui:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Sidearm policy for all 19 tools.

Tool Name navigate_ui
Category Execute
MCP Server Sidearm MCP Server
Risk Level High

View all 19 tools →

Agents calling execute-class tools like navigate_ui have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

navigate_ui is one of the high-risk operations in Sidearm. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the navigate_ui tool do? +

Look up how to perform an action in the Sidearm dashboard UI. Returns step-by-step instructions for dashboard operations such as uploading media, running searches, managing API keys, reviewing deals, buying credits, and more. Use this when the user asks how to do something in the dashboard or web app. Omit the query to get an overview of all available pages.. It is categorised as a Execute tool in the Sidearm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on navigate_ui? +

Add a rule in your Intercept YAML policy under the tools section for navigate_ui. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Sidearm MCP server.

What risk level is navigate_ui? +

navigate_ui is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit navigate_ui? +

Yes. Add a rate_limit block to the navigate_ui rule in your Intercept 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.

How do I block navigate_ui completely? +

Set action: deny in the Intercept policy for navigate_ui. 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.

What MCP server provides navigate_ui? +

navigate_ui is provided by the Sidearm MCP server (sidearmdrm/sidearm). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Sidearm

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.