Look up information about all supported timezones.
AI agents call list_timezones to retrieve information from Marketstack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static reference data (supported timezones) with no capability to modify, delete, execute code, or affect financial systems. It is a simple lookup utility typical of informational APIs. The blast radius of misuse is minimal—an agent could only retrieve timezone information, which poses no security or operational risk.
From the tool's definition Tool named 'list_timezones' with description 'Look up information about all supported timezones' — this is a straightforward data retrieval operation that queries and returns timezone reference information without any side effects.
Attacks that exploit this kind of access
Look up information about all supported timezones. It is categorised as a Read tool in the Marketstack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Marketstack MCP Server 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 Marketstack MCP Server. 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 Marketstack MCP Server MCP server (matteoantoci/mcp-marketstack). 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 →