Return Kraken's current server time (unix and RFC1123).
AI agents call get_server_time to retrieve information from Mcp Kraken without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves temporal data from the server. It does not modify any state, execute commands, move funds, or delete data. The read-only nature of the operation makes it low-risk, with negligible blast radius even if called repeatedly or unexpectedly by an AI agent.
From the tool's definition Tool returns Kraken's current server time in unix and RFC1123 formats. This is a simple query operation with no side effects, no data modification, and no account impact.
Attacks that exploit this kind of access
Return Kraken's current server time (unix and RFC1123). It is categorised as a Read tool in the Mcp Kraken MCP Server, which means it retrieves data without modifying state.
Register the Mcp Kraken MCP server in PolicyLayer and add a rule for get_server_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 Kraken. Nothing to install.
get_server_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_server_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_server_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_server_time is provided by the Mcp Kraken MCP server (xavierbeheydt/mcp-kraken). 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 →