AI agents call get_current_time to retrieve information from MCP-Demo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves the current time value without modifying, executing, or deleting any data. It is a simple informational query with no potential for misuse or unintended consequences.
From the tool's definition Tool name 'get_current_time' and description '获取当前时间' (get current time) indicate a read-only retrieval of system time with no side effects.
Attacks that exploit this kind of access
获取当前时间。. It is categorised as a Read tool in the MCP-Demo MCP Server, which means it retrieves data without modifying state.
Register the MCP-Demo MCP server in PolicyLayer and add a rule for get_current_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-Demo. Nothing to install.
get_current_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_current_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_current_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_current_time is provided by the MCP-Demo MCP server (tatocode/mcp-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_current_time is one line of MCP-Demo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →