AI agents call get_time to retrieve information from MCP Kkebi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current time without modifying any data, triggering external operations, or causing irreversible changes. It is a straightforward informational read operation with minimal security impact even if misused by an AI agent.
From the tool's definition Tool name 'get_time' and description '현재 시간을 알려줍니다' (tells the current time) indicate a simple time query operation with no side effects.
Attacks that exploit this kind of access
현재 시간을 알려줍니다. It is categorised as a Read tool in the MCP Kkebi MCP Server, which means it retrieves data without modifying state.
Register the MCP Kkebi MCP server in PolicyLayer and add a rule for get_time: 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 MCP Kkebi. Nothing to install.
get_time 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_time 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_time. 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_time is provided by the MCP Kkebi MCP server (mimsut/mcp_kkebi). 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 →