list_sites
List all WordPress sites configured in ~/.elementeer/config.json.
This record as markdown: /tools/vamerli-elementify-mcp/list-sites.md
What list_sites does on Elementify MCP
AI agents call list_sites to retrieve information from Elementify MCP 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 performs a simple read operation that retrieves configuration data about WordPress sites from a local JSON file. It has no side effects, does not modify any data, does not execute commands, and does not trigger external operations. The blast radius of misuse is minimal — an agent could learn what sites are configured, but cannot take action on them with this tool alone. This is a classic Read operation.
From the tool's definition Tool name is 'list_sites' and description states it 'List[s] all WordPress sites configured in ~/.elementeer/config.json' — a pure data retrieval operation with no modification or execution.
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 Elementify MCP, 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 Elementify MCP, apply this rule, and every list_sites call is checked against it from then on.
Questions about list_sites
List all WordPress sites configured in ~/.elementeer/config.json. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.
Register the Elementify 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 Elementify MCP. 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 Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elementify, and thousands of servers like it.
This server
Across the catalogue