Show current repository context and Wiki.js organization.
AI agents call wikijs_repository_context 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 retrieves and displays information about the current repository context and Wiki.js organizational structure. It performs no side effects, modifications, deletions, or code execution. It is purely informational (Read category). The severity is low because exposure of organizational metadata poses minimal risk—it does not enable direct data corruption, financial transactions, or destructive actions.
From the tool's definition Tool name 'wikijs_repository_context' and description 'Show current repository context and Wiki.js organization' indicate a query/retrieval operation that displays contextual information without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access wikijs_repository_context 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_repository_context:
{
"version": "1",
"default": "deny",
"tools": {
"wikijs_repository_context": {}
}
}wikijs_repository_context 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.
Show current repository context and Wiki.js organization. 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_repository_context: 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_repository_context 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_repository_context 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_repository_context. 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_repository_context 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.