High Risk →

navigate

Walk the UKHSA surveillance hierarchy one level at a time to discover valid values. Pass the levels you already know (in order: theme, sub_theme, topic, geography_type, geography) and you get back the list of options for the NEXT level. With no args it lists themes (e.g. infectious_disease, immun...

Part of the Ukhsa server.

navigate can trigger actions in Ukhsa, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE UKHSA →

Free to start. No card required.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "navigate": {
      "limits": [
        {
          "counter": "navigate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Ukhsa policy for all 23 tools.

Get this rule live on your own Ukhsa server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY UKHSA →

View all 23 tools →

These attack patterns abuse exactly the kind of access navigate gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so navigate only ever does what you allow.

SECURE UKHSA →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the navigate tool do? +

Walk the UKHSA surveillance hierarchy one level at a time to discover valid values. Pass the levels you already know (in order: theme, sub_theme, topic, geography_type, geography) and you get back the list of options for the NEXT level. With no args it lists themes (e.g. infectious_disease, immunisation, climate_and_environment, medicines). With theme="infectious_disease" it lists sub_themes (respiratory, gastrointestinal, vaccine_preventable, ...). Continue down to topics (COVID-19, Influenza, Measles, ...), geography_types (Nation, NHS Region, ...), geographies (England, ...), and finally metrics. Each item has {name, link}. Feed the chosen name into the next-level arg, then call get_metric_data once you have all six.. It is categorised as a Execute tool in the Ukhsa 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? +

Register the Ukhsa MCP server in PolicyLayer and add a rule for navigate: 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 Ukhsa. Nothing to install.

What risk level is navigate? +

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

Can I rate-limit navigate? +

Yes. Add a rate_limit block to the navigate 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.

How do I block navigate completely? +

Set action: deny in the PolicyLayer policy for navigate. 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? +

navigate is provided by the Ukhsa MCP server (https://gateway.pipeworx.io/ukhsa/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ukhsa tool call.

Deterministic rules across all 23 Ukhsa 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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.