ksef_attach_field_provenance · KSeF MCP: Risk & Policy

WHAT IT DOES

What ksef_attach_field_provenance does on KSeF MCP

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

WHY IT NEEDS A POLICY

Why ksef_attach_field_provenance needs a policy

This tool modifies draft invoice documents by attaching provenance information, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The 'require confirmation' safety gate mitigates severity from high to medium, as the operation is gated and reversible.

From the tool's definition 'Attach source-backed field provenance to a draft' indicates modification of draft invoice data by adding provenance metadata. The phrase 'require confirmation' suggests a safety gate, but the core action is creating/modifying draft state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ksef_attach_field_provenance Rate-limited

ksef_attach_field_provenance 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": {
    "ksef_attach_field_provenance": {
      "limits": [
        {
          "counter": "ksef_attach_field_provenance_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 KSeF MCP, so you can run agents against it safely.

FAQ

Questions about ksef_attach_field_provenance

What does the ksef_attach_field_provenance tool do? +

Attach source-backed field provenance to a draft and require confirmation. It is categorised as a Write tool in the KSeF MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ksef_attach_field_provenance? +

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

What risk level is ksef_attach_field_provenance? +

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

Can I rate-limit ksef_attach_field_provenance? +

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

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

ksef_attach_field_provenance is provided by the KSeF MCP server (olegtyshcneko/ksef-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.