list_gateways
AI agents call list_gateways to retrieve information from Zencontrol Cloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix conventionally indicates a read operation that retrieves and returns information without side effects. Given the control system context and presence of similar read tools on the server, this likely retrieves gateway inventory/configuration data.
From the tool's definition Tool name 'list_gateways' indicates a listing/enumeration operation with no modification capability. No description provided, but naming convention and context of sibling tools (list_devices, list_device_locations, get_* tools) suggests read-only data…
Attacks that exploit this kind of access
list_gateways. It is categorised as a Read tool in the Zencontrol Cloud MCP Server, which means it retrieves data without modifying state.
Register the Zencontrol Cloud MCP server in PolicyLayer and add a rule for list_gateways: 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 Zencontrol Cloud. Nothing to install.
list_gateways 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 list_gateways 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 list_gateways. 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.
list_gateways is provided by the Zencontrol Cloud MCP server (owretch/zencontrol-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →