complete_capture_session · Qontinui Web MCP Server MCP

WHAT IT DOES

What complete_capture_session does on Qontinui Web MCP Server

AI agents use complete_capture_session to create or update resources in Qontinui Web MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qontinui Web MCP Server environment.

WHY IT NEEDS A POLICY

Why complete_capture_session needs a policy

This tool performs a reversible modification of a capture session's state/status within the Qontinui automation system. It does not retrieve data (Read), execute external code (Execute), delete anything (Destructive), or move money (Financial).

From the tool's definition Tool description states 'Mark a capture session as complete', which is a state-changing operation that modifies the capture session record. The tool creates or updates data (marking completion status) but does not delete data or execute arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_capture_session Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "complete_capture_session": {
      "limits": [
        {
          "counter": "complete_capture_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about complete_capture_session

What does the complete_capture_session tool do? +

Mark a capture session as complete and ready for analysis. It is categorised as a Write tool in the Qontinui Web MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on complete_capture_session? +

Register the Qontinui Web MCP Server MCP server in PolicyLayer and add a rule for complete_capture_session: 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 Qontinui Web MCP Server. Nothing to install.

What risk level is complete_capture_session? +

complete_capture_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit complete_capture_session? +

Yes. Add a rate_limit block to the complete_capture_session 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 complete_capture_session completely? +

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

complete_capture_session is provided by the Qontinui Web MCP Server MCP server (qontinui/qontinui-web-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.