lookup_weather
Get current weather for a city (temperature, conditions, humidity, wind). No API key required. Use for travel, scheduling, or notification agents. Example call: {"city": "Tokyo"} Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/lookup-weather.md
What lookup_weather does on GoCreative Agent API
AI agents call lookup_weather to retrieve information from GoCreative Agent API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
city | string | Yes |
Parameters from the server's own tool schema.
Why lookup_weather is rated Low
This tool retrieves read-only weather information with no side effects. It does not create, modify, delete, or execute operations. The low cost and explicit read-only nature of weather data lookup confirms Read category. Severity is low because misuse (e.g., querying many cities) has minimal blast radius—it only incurs financial costs, which are capped by the per-call pricing model.
From the tool's definition Tool description states 'Get current weather for a city (temperature, conditions, humidity, wind)' with no mention of modification, deletion, or execution capabilities. The example call shows simple parameter input to retrieve data.
Attacks that exploit this kind of access
The rule that runs lookup_weather safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoCreative Agent API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lookup_weather, this is the rule to start with:
lookup_weather is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GoCreative Agent API, apply this rule, and every lookup_weather call is checked against it from then on.
Questions about lookup_weather
Get current weather for a city (temperature, conditions, humidity, wind). No API key required. Use for travel, scheduling, or notification agents. Example call: {"city": "Tokyo"} Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the GoCreative Agent API MCP Server, which means it retrieves data without modifying state.
lookup_weather accepts 1 parameter: city. Required: city. The full parameter table on this page comes from the server's own tool schema.
Register the GoCreative Agent API MCP server in PolicyLayer and add a rule for lookup_weather: 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 GoCreative Agent API. Nothing to install.
lookup_weather 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 lookup_weather 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 lookup_weather. 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.
lookup_weather is provided by the GoCreative Agent API MCP server (https://api.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoCreative Agent API, and thousands of servers like it.
This server
Across the catalogue