List common available timezones
AI agents call list_timezones to retrieve information from MCP HTTP Server Demo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves timezone information without modifying any data, executing code, or triggering external operations. It is a straightforward query/list operation with minimal risk if misused—an AI agent cannot cause harm by requesting timezone lists.
From the tool's definition Tool name and description explicitly state 'List common available timezones' — a read-only operation that retrieves enumerated data with no side effects or state modifications.
Attacks that exploit this kind of access
List common available timezones. It is categorised as a Read tool in the MCP HTTP Server Demo MCP Server, which means it retrieves data without modifying state.
Register the MCP HTTP Server Demo MCP server in PolicyLayer and add a rule for list_timezones: 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 HTTP Server Demo. Nothing to install.
list_timezones 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 list_timezones 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 list_timezones. 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.
list_timezones is provided by the MCP HTTP Server Demo MCP server (mlvalidationdebug/mcp-server-http-demo). 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 →