ksef_test_connection_check · KSeF MCP: Risk & Policy

WHAT IT DOES

What ksef_test_connection_check does on KSeF MCP

AI agents invoke ksef_test_connection_check to trigger actions in KSeF MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why ksef_test_connection_check needs a policy

The tool performs an authentication action against an external system (KSeF TEST environment) and persists state ('persist readiness'), which constitutes triggering an external operation with side effects. It is not a pure read — it writes/persists session or readiness state. It does not create invoices directly, but it executes an auth flow and stores results, placing it in Execute rather than Write or Read.

From the tool's definition Authenticate to KSeF TEST and persist readiness before invoice XML generation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ksef_test_connection_check Rate-limited

ksef_test_connection_check stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_test_connection_check": {
      "limits": [
        {
          "counter": "ksef_test_connection_check_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_test_connection_check

What does the ksef_test_connection_check tool do? +

Authenticate to KSeF TEST and persist readiness before invoice XML generation. It is categorised as a Execute tool in the KSeF MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ksef_test_connection_check? +

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

ksef_test_connection_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ksef_test_connection_check? +

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

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

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