send_order_for_approval · Kwork MCP: Risk & Policy

WHAT IT DOES

What send_order_for_approval does on Kwork

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

WHY IT NEEDS A POLICY

Why send_order_for_approval needs a policy

This tool creates or modifies order records on the Kwork marketplace by transitioning an order to an approval state. This is reversible (approval can be withdrawn or orders can be cancelled), making it Write rather than Destructive or Execute. Severity is medium because misuse could cause financial confusion or workflow disruption on the platform, though it doesn't directly move money.

From the tool's definition Tool name 'send_order_for_approval' indicates it modifies order state by submitting an order for approval—a create/modify action on marketplace data. No description provided to clarify scope.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_order_for_approval Rate-limited

send_order_for_approval 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": {
    "send_order_for_approval": {
      "limits": [
        {
          "counter": "send_order_for_approval_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 Kwork, so you can run agents against it safely.

FAQ

Questions about send_order_for_approval

What does the send_order_for_approval tool do? +

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

How do I enforce a policy on send_order_for_approval? +

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

What risk level is send_order_for_approval? +

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

Can I rate-limit send_order_for_approval? +

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

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

send_order_for_approval is provided by the Kwork MCP server (simonether/kwork-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.