Manage optional agent workflow state for this vault (${vaultScope}): status, transition, history, reset. Typical flow: search → open_note → save → done; read vault://overview for usage guidance.
AI agents use workflow to create or update resources in Mcp Markdown Vault — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Markdown Vault environment.
The tool manages workflow state including transitions and resets. 'Reset' could be considered destructive, but in the context of workflow state tracking it is reversible state management. The primary operations (status, transition, history, reset) are Write-level operations modifying workflow metadata rather than user content. Not Execute since it doesn't run code or external operations.
From the tool's definition Manage optional agent workflow state... status, transition, history, reset
Documented attack patterns abuse exactly the kind of access workflow 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 workflow:
{
"version": "1",
"default": "deny",
"tools": {
"workflow": {
"limits": [
{
"counter": "workflow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}workflow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage optional agent workflow state for this vault (${vaultScope}): status, transition, history, reset. Typical flow: search → open_note → save → done; read vault://overview for usage guidance. It is categorised as a Write tool in the Mcp Markdown Vault MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Markdown Vault MCP server in PolicyLayer and add a rule for workflow: 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.
workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workflow 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 workflow. 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.
workflow 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.