Low Risk

amap_route_drive

Get driving route between two points using 高德地图. Args: origin_lng: Origin longitude. origin_lat: Origin latitude. dest_lng: Destination longitude. dest_lat: Destination latitude.

How to control amap_route_drive ↓

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

Low Risk

This is a straightforward geolocation query tool that retrieves pre-computed route data without side effects. It does not create, modify, delete, or execute operations. The severity is low because misuse would only expose routing information, posing minimal risk to data integrity or security.

From the tool's definition Tool name 'amap_route_drive' and description indicate it retrieves driving route data between two geographic points.

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

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

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

amap_route_drive 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 autoMate — 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.

Go deeper

What does the amap_route_drive tool do? +

Get driving route between two points using 高德地图. Args: origin_lng: Origin longitude. origin_lat: Origin latitude. dest_lng: Destination longitude. dest_lat: Destination latitude. It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on amap_route_drive? +

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

What risk level is amap_route_drive? +

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

Can I rate-limit amap_route_drive? +

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

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

amap_route_drive is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every autoMate tool call.

Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

128 autoMate tools catalogued and risk-classified — across an index of 42,500+ 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.