list_watches

List your watches AND keep them alive (the inactivity check-in). Requires handle + secret — the URLs you monitor are private.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/list-watches.md

WHAT IT DOES

What list_watches does on Gateway

AI agents call list_watches to retrieve information from Gateway 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
`handle`	string	Yes

Parameters from the server's own tool schema.

RISK

Why list_watches is rated Low

This tool retrieves a list of watches and performs a passive keep-alive ping. No data is created, modified, deleted, or irreversibly changed. While it requires credentials to access private URLs, the core action is read-only enumeration with a side effect of resetting inactivity timers—a non-destructive maintenance operation. This is classic Read category behavior.

From the tool's definition Tool description explicitly states 'List your watches' — a retrieval operation. The 'keep them alive' action is a maintenance check-in, not a modification of the watches themselves.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_watches safely

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

list_watches Allowed

list_watches is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_watches": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every list_watches call is checked against it from then on.

FAQ

Questions about list_watches

What does the list_watches tool do? +

List your watches AND keep them alive (the inactivity check-in). Requires handle + secret — the URLs you monitor are private. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.

What parameters does list_watches accept? +

list_watches accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_watches? +

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

What risk level is list_watches? +

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

Can I rate-limit list_watches? +

Yes. Add a rate_limit block to the list_watches 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 list_watches completely? +

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

list_watches is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →