This record as markdown: /tools/io-github-2s-io-mcp/watchers.flight-status.md
What watchers.flight-status does on Mcp
AI agents call watchers.flight-status to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why watchers.flight-status is rated Low
This tool queries and retrieves flight status data. Despite the unfished description (likely cut off), the core function is to obtain information about a flight. Even as a watcher/subscription, it only returns data reactively without creating side effects, modifying state, or executing code. Typical read operation for aviation data lookup.
From the tool's definition Tool description states 'get a signed callback when a flight' — retrieves flight status information via a watcher/subscription mechanism. No modification, deletion, or execution of external systems implied.
Attacks that exploit this kind of access
The rule that runs watchers.flight-status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For watchers.flight-status, this is the rule to start with:
watchers.flight-status 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 Mcp, apply this rule, and every watchers.flight-status call is checked against it from then on.
Questions about watchers.flight-status
WATCHER: get a signed callback when a flight\. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for watchers.flight-status: 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. Nothing to install.
watchers.flight-status 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 watchers.flight-status 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 watchers.flight-status. 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.
watchers.flight-status is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue