System administration for this vault (${vaultScope}). Actions: status (indexing/backlinks/workflow health), reindex (async rebuild), overview (folder tree), overview_status (meta/overview.md state), prepare_overview (gather evidence), save_overview (persist host-written overview).
AI agents invoke system to trigger actions in Mcp Markdown Vault. 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.
The tool performs system administration operations including triggering async reindex rebuilds and persisting overview data. 'reindex' triggers an external operation (async rebuild of the index), 'save_overview' writes/persists data, and 'prepare_overview' gathers evidence.
From the tool's definition reindex (async rebuild), status (indexing/backlinks/workflow health), prepare_overview (gather evidence), save_overview (persist host-written overview)
Documented attack patterns abuse exactly the kind of access system gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Markdown Vault, and nothing reaches the server without passing your rules. This is the rule we recommend for system:
{
"version": "1",
"default": "deny",
"tools": {
"system": {
"limits": [
{
"counter": "system_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}system 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.
System administration for this vault (${vaultScope}). Actions: status (indexing/backlinks/workflow health), reindex (async rebuild), overview (folder tree), overview_status (meta/overview.md state), prepare_overview (gather evidence), save_overview (persist host-written overview). It is categorised as a Execute tool in the Mcp Markdown Vault MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Markdown Vault MCP server in PolicyLayer and add a rule for system: 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 Mcp Markdown Vault. Nothing to install.
system 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 system 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 system. 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.
system is provided by the Mcp Markdown Vault MCP server (wirux/mcp-markdown-vault). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Markdown Vault, 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.
5 Mcp Markdown Vault tools catalogued and risk-classified — across an index of 43,000+ MCP servers.