AI agents invoke wiki to trigger actions in Local Rag. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a workflow rebuild operation, which is an automated process that can modify state and have side effects. It is not a simple read operation (does not just retrieve data), not a reversible write (rebuilds suggest overwriting), and the execution effects are contingent on the workflow's implementation and arguments.
From the tool's definition Tool name 'wiki' and description 'Run the wiki rebuild workflow' indicate execution of a workflow process.
Documented attack patterns abuse exactly the kind of access wiki gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for wiki:
{
"version": "1",
"default": "deny",
"tools": {
"wiki": {
"limits": [
{
"counter": "wiki_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} wiki stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run the wiki rebuild workflow. The. It is categorised as a Execute tool in the Local Rag MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Local Rag MCP server in PolicyLayer and add a rule for wiki: 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 Local Rag. Nothing to install.
wiki is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wiki 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. 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 is provided by the Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local Rag, 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.
29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.