# get-current-time

現在の日時を取得するツール

Agent View of the PolicyLayer registry record for `get-current-time`. HTML page: https://policylayer.com/tools/109naoki-minimal-mcp-server/get-current-time

## Facts

- Tool: `get-current-time`
- Server: Minimal (`109naoki/minimal-mcp-server`) — https://policylayer.com/tools/109naoki-minimal-mcp-server.md
- Homepage: https://github.com/109naoki/minimal-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get-current-time",
    "arguments": {}
  }
}
```

## Why get-current-time is rated Low

This tool only queries and returns the current time, which is a read-only operation. It does not modify, execute, delete, or create data, nor does it commit any financial obligations. The potential for misuse is minimal since time data is non-sensitive and cannot be manipulated by the requester.

From the tool's own definition: "Tool name 'get-current-time' and description '現在の日時を取得するツール' (retrieves current date and time) indicate a simple data retrieval operation with no side effects."

## Use case

AI agents call get-current-time to retrieve information from Minimal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Minimal:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-current-time": {}
  }
}
```

## Other tools on Minimal (2)

- `echo` — Read — https://policylayer.com/tools/109naoki-minimal-mcp-server/echo.md
- `search-wikipedia` — Read — https://policylayer.com/tools/109naoki-minimal-mcp-server/search-wikipedia.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=109naoki-minimal-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/109naoki-minimal-mcp-server