Low Risk

get_navigation_history

Get user navigation history

How to control get_navigation_history ↓

What get_navigation_history does on React Tools

AI agents call get_navigation_history to retrieve information from React Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_navigation_history needs a policy

This tool retrieves and queries navigation history data without creating, modifying, deleting, executing code, or committing financial obligations. It is a straightforward read operation that returns existing information about user navigation patterns. The low severity reflects minimal blast radius—misuse would expose historical navigation patterns but cannot directly harm systems or data.

From the tool's definition Tool name 'get_navigation_history' and description 'Get user navigation history' indicate retrieval of historical data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_navigation_history gives an agent:

How to control get_navigation_history

PolicyLayer is an MCP gateway — it sits between your AI agents and React Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for get_navigation_history:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_navigation_history": {}
  }
}

get_navigation_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register React Tools — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_navigation_history

What does the get_navigation_history tool do? +

Get user navigation history. It is categorised as a Read tool in the React Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_navigation_history? +

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

What risk level is get_navigation_history? +

get_navigation_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_navigation_history? +

Yes. Add a rate_limit block to the get_navigation_history 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 get_navigation_history completely? +

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

get_navigation_history is provided by the React Tools MCP server (mcp-fe/mcp-fe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every React Tools tool call.

Start from React Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

20 React Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.