upsert_partner · Cockpit MCP: Risk & Policy

WHAT IT DOES

What upsert_partner does on Cockpit

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

WHY IT NEEDS A POLICY

Why upsert_partner needs a policy

The tool creates or updates partner records in a financial accounting system (freee). While reversible (can be corrected via corrections or deletions in typical accounting software), upsert operations that auto-create master data records in accounting contexts pose significant operational risk if misused by an AI agent (e.g., creating duplicate or fraudulent partner entries that inflate transaction records or…

From the tool's definition Tool performs 'auto-creation in freee' and 'create' operation with 'upsert' (update or insert) semantics on partner master data (取引先マスタ). This modifies accounting data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upsert_partner Rate-limited

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

FAQ

Questions about upsert_partner

What does the upsert_partner tool do? +

取引先マスタ auto-creation in freee. Fuzzy match against existing partners; if new, create. Returns partner_id. It is categorised as a Write tool in the Cockpit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upsert_partner? +

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

What risk level is upsert_partner? +

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

Can I rate-limit upsert_partner? +

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

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

upsert_partner is provided by the Cockpit MCP server (michielinksee/kansei-link-cockpit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.