full_document_workflow · Auto-Snap MCP: Risk & Policy

WHAT IT DOES

What full_document_workflow does on Auto-Snap MCP

AI agents invoke full_document_workflow to trigger actions in Auto-Snap MCP. 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.

WHY IT NEEDS A POLICY

Why full_document_workflow needs a policy

The description is empty, so classification relies on the tool name and server context. 'full_document_workflow' implies executing a complete automated workflow combining multiple operations (capture, convert, extract). Given sibling tools include capture, convert_to_pdf, process_images, and directory_to_pdf, this tool likely chains these operations together.

From the tool's definition Tool name 'full_document_workflow' and server context involving screenshot capture, PDF conversion, and text extraction suggest a multi-step automated pipeline execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

full_document_workflow Rate-limited

full_document_workflow 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "full_document_workflow": {
      "limits": [
        {
          "counter": "full_document_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Auto-Snap MCP, so you can run agents against it safely.

FAQ

Questions about full_document_workflow

What does the full_document_workflow tool do? +

full_document_workflow. It is categorised as a Execute tool in the Auto-Snap MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on full_document_workflow? +

Register the Auto-Snap MCP server in PolicyLayer and add a rule for full_document_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 Auto-Snap MCP. Nothing to install.

What risk level is full_document_workflow? +

full_document_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit full_document_workflow? +

Yes. Add a rate_limit block to the full_document_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.

How do I block full_document_workflow completely? +

Set action: deny in the PolicyLayer policy for full_document_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.

What MCP server provides full_document_workflow? +

full_document_workflow is provided by the Auto-Snap MCP server (povedaaqui/auto-snap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.