Get wiki page details including body content. Two API endpoints supported: 1. With pageId only: GET /wiki/v1/pages/{page-id} 2. With wikiId + pageId: GET /wiki/v1/wikis/{wiki-id}/pages/{page-id} Returns: id, wikiId, version, subject, body (mimeType, content), creator, referrers, files, images.
AI agents call get-wiki-page to retrieve information from Dooray MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval operation. GET requests retrieve wiki page information without creating, modifying, deleting, or executing any operations. The return values are informational metadata and content. There is no side effect or state change. Low severity because unauthorized access to wiki pages presents information disclosure risk, but the tool itself performs only queries.
From the tool's definition Tool name is 'get-wiki-page' and description states 'Get wiki page details including body content.' The API endpoints are both GET requests with no parameters that modify state.
Attacks that exploit this kind of access
Get wiki page details including body content. Two API endpoints supported: 1. With pageId only: GET /wiki/v1/pages/{page-id} 2. With wikiId + pageId: GET /wiki/v1/wikis/{wiki-id}/pages/{page-id} Returns: id, wikiId, version, subject, body (mimeType, content), creator, referrers, files, images. It is categorised as a Read tool in the Dooray MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dooray MCP Server MCP server in PolicyLayer and add a rule for get-wiki-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 Dooray MCP Server. Nothing to install.
get-wiki-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-wiki-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-wiki-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-wiki-page is provided by the Dooray MCP Server MCP server (jhl8041/dooray-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →