list_pages
A read tool on the Enterprise-Multi-Agent-Engine MCP server.
This record as markdown: /tools/enterprise-multi-agent-engine/list-pages.md
What list_pages does on Enterprise-Multi-Agent-Engine
AI agents call list_pages to retrieve information from Enterprise-Multi-Agent-Engine without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_pages is rated Low
The tool lists pages, which is a query/retrieval operation with no side effects. No description is provided, but the name and context of sibling read-only tools (get, search, list) strongly indicate this is a data retrieval operation. Confidence is slightly reduced due to lack of explicit description, but the naming pattern is clear.
From the tool's definition Tool name 'list_pages' indicates retrieval of page listings without modification. Sibling tools like 'get_page_content', 'list_mikecreighton_website_pages', and 'search_pages' all suggest read-only operations over website content.
Attacks that exploit this kind of access
The rule that runs list_pages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enterprise-Multi-Agent-Engine, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_pages, this is the rule to start with:
list_pages 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 Enterprise-Multi-Agent-Engine, apply this rule, and every list_pages call is checked against it from then on.
Questions about list_pages
list_pages is a read tool on the Enterprise-Multi-Agent-Engine MCP server. It is categorised as a Read tool in the Enterprise-Multi-Agent-Engine MCP Server, which means it retrieves data without modifying state.
Register the Enterprise-Multi-Agent-Engine MCP server in PolicyLayer and add a rule for list_pages: 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 Enterprise-Multi-Agent-Engine. Nothing to install.
list_pages 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_pages 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_pages. 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_pages is provided by the Enterprise-Multi-Agent-Engine MCP server (Mojtaba-Dehghani/Enterprise-Multi-Agent-Engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enterprise-Multi-Agent-Engine, and thousands of servers like it.
This server
Across the catalogue