Check the status of the Wiki.js connection and authentication.
AI agents call wikijs_connection_status to retrieve information from Wiki Js without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only diagnostic check of connection and authentication status. It retrieves information about the current state of the Wiki.js connection without modifying any data, executing code, or causing side effects. The low severity reflects that even if misused, checking connection status poses minimal risk—it cannot delete, modify, or execute arbitrary operations.
From the tool's definition Tool name 'wikijs_connection_status' and description 'Check the status of the Wiki.js connection and authentication' indicate a query/status check operation with no data modification, creation, deletion, or execution of arbitrary operations.
Documented attack patterns abuse exactly the kind of access wikijs_connection_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wiki Js, and nothing reaches the server without passing your rules. This is the rule we recommend for wikijs_connection_status:
{
"version": "1",
"default": "deny",
"tools": {
"wikijs_connection_status": {}
}
} wikijs_connection_status 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.
Check the status of the Wiki.js connection and authentication. It is categorised as a Read tool in the Wiki Js MCP Server, which means it retrieves data without modifying state.
Register the Wiki Js MCP server in PolicyLayer and add a rule for wikijs_connection_status: 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 Wiki Js. Nothing to install.
wikijs_connection_status 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 wikijs_connection_status 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 wikijs_connection_status. 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.
wikijs_connection_status is provided by the Wiki Js MCP server (talosdeus/wiki-js-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Wiki Js tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Wiki Js tools catalogued and risk-classified — across an index of 42,500+ MCP servers.