지역명이나 강 이름으로 관측소 검색 (실제 코드 포함)
AI agents call search_water_station_by_name to retrieve information from HRFCO Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search query against hydrological station data, returning matching observatories by name. This is a read-only operation that retrieves data without side effects. No code execution, data modification, deletion, or financial impact is indicated. The mention of 'actual code' in the description likely refers to the tool's implementation details, not code execution capability.
From the tool's definition Tool name 'search_water_station_by_name' and description indicate querying/searching for water station observatory information by geographic or river name.
Attacks that exploit this kind of access
지역명이나 강 이름으로 관측소 검색 (실제 코드 포함). It is categorised as a Read tool in the HRFCO Service MCP Server, which means it retrieves data without modifying state.
Register the HRFCO Service MCP server in PolicyLayer and add a rule for search_water_station_by_name: 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 HRFCO Service. Nothing to install.
search_water_station_by_name 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_water_station_by_name 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_water_station_by_name. 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_water_station_by_name is provided by the HRFCO Service MCP server (kwenhwang/hrfco-service). 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 →