AI agents call search_stations_around to retrieve information from Opinet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves location-based information about nearby gas stations given coordinates. It performs a read operation analogous to a geospatial search or filter query. There is no data modification, code execution, deletion, or financial transaction involved. The blast radius of misuse is minimal—an attacker could only gather publicly available fuel station location data.
From the tool's definition Tool description states it searches (검색) gas stations around specified coordinates within a radius. The action is purely retrieval-based with no modification or execution capabilities. The tool queries existing fuel station data without side effects.
Attacks that exploit this kind of access
특정 KATEC 좌표(x, y)를 중심으로 반경 내 주유소를 검색합니다. 좌표는 KATEC 좌표계 기준입니다 (WGS84 위경도 아님). It is categorised as a Read tool in the Opinet MCP Server, which means it retrieves data without modifying state.
Register the Opinet MCP server in PolicyLayer and add a rule for search_stations_around: 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 Opinet. Nothing to install.
search_stations_around 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 search_stations_around 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 search_stations_around. 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.
search_stations_around is provided by the Opinet MCP server (kimjintak/opinet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →