slow-weather

What slow-weather does on Frontmcp

AI agents call slow-weather to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why slow-weather is rated Low

This is a read-only operation that queries and returns weather information with simulated delay. It has no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is negligible; an AI agent calling this repeatedly would waste compute resources but cause no meaningful harm. Severity is low because it is a benign mock tool for demonstration or testing purposes.

From the tool's definition Tool is described as a 'weather lookup', which retrieves data. The prefix 'Pretend-slow' indicates it is a mock/test tool that simulates latency. No language in the description suggests data modification, deletion, code execution, or financial operations.

The rule that runs slow-weather safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For slow-weather, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "slow-weather": {}
  }
}

Questions about slow-weather