submit_offer · Kwork MCP: Risk & Policy

WHAT IT DOES

What submit_offer does on Kwork

AI agents use submit_offer 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 submit_offer needs a policy

Submitting an offer on a freelance marketplace creates a binding or semi-binding commitment to provide services at specified terms. This is a Write operation (creates reversible marketplace data), but severity is high because misuse could result in unintended financial commitments, reputational damage, or resource obligations.

From the tool's definition Tool name 'submit_offer' combined with server description indicating it 'submit offers' on a freelance marketplace. Sibling tools include 'delete_offer' and 'edit_offer', confirming this modifies marketplace state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_offer Rate-limited

submit_offer 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": {
    "submit_offer": {
      "limits": [
        {
          "counter": "submit_offer_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 submit_offer

What does the submit_offer tool do? +

submit_offer. 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 submit_offer? +

Register the Kwork MCP server in PolicyLayer and add a rule for submit_offer: 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 submit_offer? +

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

Can I rate-limit submit_offer? +

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

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

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