Start a local preview server for Quarkdown documents with live reload
AI agents invoke preview_server to trigger actions in Quarkdown MCP Server. 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.
Starting a local server is an Execute action: it runs an external operation whose effects depend on arguments (port number, document path, etc.) and cannot be trivially undone without stopping the process. It is not Destructive (no data loss), Write (not creating/modifying persistent data), or Read (actively initiates a process).
From the tool's definition Tool description states 'Start a local preview server' — this initiates a process/server, which is an external operation with side effects (binding ports, resource allocation, network listeners).
Documented attack patterns abuse exactly the kind of access preview_server gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Quarkdown MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for preview_server:
{
"version": "1",
"default": "deny",
"tools": {
"preview_server": {
"limits": [
{
"counter": "preview_server_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} preview_server 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.
Start a local preview server for Quarkdown documents with live reload. It is categorised as a Execute tool in the Quarkdown MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Quarkdown MCP Server MCP server in PolicyLayer and add a rule for preview_server: 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 Quarkdown MCP Server. Nothing to install.
preview_server 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 preview_server 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 preview_server. 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.
preview_server is provided by the Quarkdown MCP Server MCP server (lillard01/quarkdown-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Quarkdown MCP Server, 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 Quarkdown MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.