get_im_log

获取 IM 上下线记录

SERVERIkuai SOURCEgxxHuang/ikuai-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ikuai-mcp-server/get-im-log.md

WHAT IT DOES

What get_im_log does on Ikuai

AI agents call get_im_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.

RISK

Why get_im_log is rated Low

Even though get_im_log only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_im_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_im_log, this is the rule to start with:

get_im_log Allowed

get_im_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_im_log": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ikuai, apply this rule, and every get_im_log call is checked against it from then on.

FAQ

Questions about get_im_log

What does the get_im_log tool do? +

获取 IM 上下线记录. It is categorised as a Read tool in the Ikuai MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_im_log? +

Register the Ikuai MCP server in PolicyLayer and add a rule for get_im_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.

What risk level is get_im_log? +

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

Can I rate-limit get_im_log? +

Yes. Add a rate_limit block to the get_im_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.

How do I block get_im_log completely? +

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

What MCP server provides get_im_log? +

get_im_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.

KEEP EXPLORING

More on Ikuai, and thousands of servers like it.

This server

All 229 Ikuai tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →