This record as markdown: /tools/baidu-map/navi-location.md
What navi_location does on Baidu Map
AI agents call navi_location to retrieve information from Baidu Map without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why navi_location is rated Low
The tool appears to return location/navigation data given longitude and latitude coordinates, consistent with a Read operation. The description is minimal and uninformative, so confidence is lowered. No side effects, writes, or destructive actions are indicated. On a Baidu Map MCP server alongside tools like 'address', 'city', 'business_info', this fits a pattern of geographic data retrieval.
From the tool's definition Tool name 'navi_location' and description '{ lng: number, lat: number }' suggest it retrieves or provides a navigation location based on coordinates.
Attacks that exploit this kind of access
The rule that runs navi_location safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Baidu Map, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For navi_location, this is the rule to start with:
navi_location is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Baidu Map, apply this rule, and every navi_location call is checked against it from then on.
Questions about navi_location
{ lng: number, lat: number }. It is categorised as a Read tool in the Baidu Map MCP Server, which means it retrieves data without modifying state.
Register the Baidu Map MCP server in PolicyLayer and add a rule for navi_location: 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 Baidu Map. Nothing to install.
navi_location is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the navi_location 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 navi_location. 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.
navi_location is provided by the Baidu Map MCP server (@baidumap/mcp-server-baidu-map). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Baidu Map, and thousands of servers like it.
This server
Across the catalogue