get_all_signals

Run a full scan across all supported cities and rank top weather-market signals.

Server Weather Edge MCP Server rjw34/weather-edge-mcp
Category Read
Risk class Low
Parameters 00 required

What get_all_signals does on Weather Edge MCP Server

AI agents call get_all_signals to retrieve information from Weather Edge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_all_signals needs a policy

This tool retrieves and analyzes weather forecast data to identify market signals. It performs read-only operations (scanning, ranking) across a dataset without creating, modifying, deleting, or executing external code. The worst-case misuse is an agent making poor financial decisions based on retrieved signals, but the tool itself has no write/execute/destructive capability and commits no financial transactions.

From the tool's definition Tool description states 'Run a full scan across all supported cities and rank top weather-market signals' - a retrieval and ranking operation with no modification of data. Named 'get_all_signals' emphasizing data retrieval.

Questions about get_all_signals

What does the get_all_signals tool do? +

Run a full scan across all supported cities and rank top weather-market signals. It is categorised as a Read tool in the Weather Edge MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_all_signals? +

Register the Weather Edge MCP Server MCP server in PolicyLayer and add a rule for get_all_signals: 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 Weather Edge MCP Server. Nothing to install.

What risk level is get_all_signals? +

get_all_signals is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_all_signals? +

Yes. Add a rate_limit block to the get_all_signals 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.

How do I block get_all_signals completely? +

Set action: deny in the PolicyLayer policy for get_all_signals. 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.

What MCP server provides get_all_signals? +

get_all_signals is provided by the Weather Edge MCP Server MCP server (rjw34/weather-edge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.