list_clients
A read tool on the API-Central MCP server.
This record as markdown: /tools/secure-ssid-centralmcp/list-clients.md
What list_clients does on API-Central
AI agents call list_clients to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_clients is rated Low
The tool name 'list_clients' has a clear semantic pattern indicating data retrieval. In network management contexts, 'list_clients' typically enumerates connected devices or client devices on a network. No write, delete, execution, or financial operations are implied. The blast radius if misused is low—an AI agent querying client lists causes no harm.
From the tool's definition Tool name 'list_clients' follows the 'list_*' pattern, which is inherently a read operation that retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs list_clients safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_clients, this is the rule to start with:
list_clients 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 API-Central, apply this rule, and every list_clients call is checked against it from then on.
Questions about list_clients
list_clients is a read tool on the API-Central MCP server. 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_clients: 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_clients 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_clients 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_clients. 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_clients 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.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue