mark_order_complete · Qanat Goose MCP Extension MCP

WHAT IT DOES

What mark_order_complete does on Qanat Goose MCP Extension

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

WHY IT NEEDS A POLICY

Why mark_order_complete needs a policy

This tool modifies order state from incomplete to complete. While not destructive (doesn't delete data), it changes order records and likely triggers downstream operations (fulfillment, payment settlement). The lack of description lowers confidence slightly, but the name and integration context (Square orders) clearly indicate a write operation that affects business-critical state.

From the tool's definition Tool name 'mark_order_complete' and context of Square orders management system; sibling tools include 'process_refund' and 'toggle_item_status', indicating state-modification capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_order_complete Rate-limited

mark_order_complete 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": {
    "mark_order_complete": {
      "limits": [
        {
          "counter": "mark_order_complete_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 Qanat Goose MCP Extension, so you can run agents against it safely.

FAQ

Questions about mark_order_complete

What does the mark_order_complete tool do? +

mark_order_complete. It is categorised as a Write tool in the Qanat Goose MCP Extension MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_order_complete? +

Register the Qanat Goose MCP Extension MCP server in PolicyLayer and add a rule for mark_order_complete: 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 Qanat Goose MCP Extension. Nothing to install.

What risk level is mark_order_complete? +

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

Can I rate-limit mark_order_complete? +

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

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

mark_order_complete is provided by the Qanat Goose MCP Extension MCP server (professordnyc/qanat-goose-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.