list_sites
Return sites with IDs, names, and location fields (paginated).
This record as markdown: /tools/secure-ssid-centralmcp/list-sites.md
What list_sites does on API-Central
AI agents call list_sites 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_sites is rated Low
This tool retrieves and lists site information (IDs, names, locations) in a paginated format. It performs a query operation with no data modification, deletion, code execution, or financial impact. The read-only nature and minimal sensitivity of site metadata information (standard identifiers and location data) result in low severity classification.
From the tool's definition Tool name is 'list_sites' and description states 'Return sites with IDs, names, and location fields (paginated)' - this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_sites 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_sites, this is the rule to start with:
list_sites 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_sites call is checked against it from then on.
Questions about list_sites
Return sites with IDs, names, and location fields (paginated). 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_sites: 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_sites 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_sites 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_sites. 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_sites 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