get_page
A read tool on the Enterprise-Multi-Agent-Engine MCP server.
This record as markdown: /tools/enterprise-multi-agent-engine/get-page.md
What get_page does on Enterprise-Multi-Agent-Engine
AI agents call get_page 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 get_page is rated Low
This tool retrieves wiki page content with no side effects. It fits the Read category: queries data without modification, deletion, or execution of arbitrary code. Severity is low because wiki content is typically public and non-sensitive; misuse would at most retrieve information already publicly available.
From the tool's definition Tool name 'get_page' combined with server description stating it 'retrieves Minecraft Wiki content in multiple formats (wikitext, HTML, markdown)'. The server is documented as enabling 'searching and retrieving' wiki content.
Attacks that exploit this kind of access
The rule that runs get_page 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 get_page, this is the rule to start with:
get_page 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 get_page call is checked against it from then on.
Questions about get_page
get_page 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 get_page: 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.
get_page 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 get_page 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 get_page. 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.
get_page 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