List GW security policies (bounded by default).
AI agents call list_gw_policies to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves security policy information from a gateway without modifying, executing, or deleting any resources. The 'bounded by default' qualifier suggests the query scope is controlled, further reducing risk. The action is read-only information gathering, placing it squarely in the Read category with low severity.
From the tool's definition Tool name 'list_gw_policies' and description 'List GW security policies (bounded by default)' indicate a query/retrieval operation. The verb 'list' and the context of network operations policy enumeration show no side effects—only data retrieval.
Attacks that exploit this kind of access
List GW security policies (bounded by default). It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for list_gw_policies: 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 API-Central. Nothing to install.
list_gw_policies 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_gw_policies 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_gw_policies. 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_gw_policies is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →