AI agents call wiki_read_page to retrieve information from Shellgate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries wiki content without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with no capability to alter state or trigger external effects. Minimal blast radius if misused—only information disclosure risk is limited to wiki content already stored in the system.
From the tool's definition Tool name 'wiki_read_page' and description 'Read a wiki page' indicate retrieval of existing data with no side effects.
Documented attack patterns abuse exactly the kind of access wiki_read_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shellgate, and nothing reaches the server without passing your rules. This is the rule we recommend for wiki_read_page:
{
"version": "1",
"default": "deny",
"tools": {
"wiki_read_page": {}
}
}wiki_read_page is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read a wiki page. It is categorised as a Read tool in the Shellgate MCP Server, which means it retrieves data without modifying state.
Register the Shellgate MCP server in PolicyLayer and add a rule for wiki_read_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 Shellgate. Nothing to install.
wiki_read_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 wiki_read_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 wiki_read_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.
wiki_read_page is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shellgate, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 Shellgate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.