This record as markdown: /tools/ikuai-mcp-server/get-url-browsing-log.md
What get_url_browsing_log does on Ikuai
AI agents call get_url_browsing_log to retrieve information from Ikuai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_url_browsing_log is rated Low
This tool retrieves historical browsing logs from the router. While it is a Read operation with no data modification, the severity is high because browsing history is sensitive personal information that could expose private user activities, visited websites, and behavioral patterns. An AI agent with access could exfiltrate extensive user privacy data, justifying the high severity despite the Read category.
From the tool's definition Tool name 'get_url_browsing_log' and description '获取网址浏览记录' (retrieves URL browsing logs) indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_url_browsing_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ikuai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_url_browsing_log, this is the rule to start with:
get_url_browsing_log 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 Ikuai, apply this rule, and every get_url_browsing_log call is checked against it from then on.
Questions about get_url_browsing_log
获取网址浏览记录. It is categorised as a Read tool in the Ikuai MCP Server, which means it retrieves data without modifying state.
Register the Ikuai MCP server in PolicyLayer and add a rule for get_url_browsing_log: 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 Ikuai. Nothing to install.
get_url_browsing_log 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 get_url_browsing_log 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 get_url_browsing_log. 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.
get_url_browsing_log is provided by the Ikuai MCP server (gxxHuang/ikuai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ikuai, and thousands of servers like it.
This server
Across the catalogue