AI agents call ksef_validate_invoice_draft to retrieve information from KSeF MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs validation—inspecting invoice draft data for completeness against schema or business rules. This is a read-like operation with no side effects: it does not create, modify, delete, or execute code. The purpose is informational (determining if a draft is valid) before submission. Even if validation were to fail, no data is changed.
From the tool's definition Tool name and description indicate validation/checking behavior: 'validate invoice draft completeness before XML preparation.' Validation is a read-only operation that checks data against rules without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Validate invoice draft completeness before XML preparation. It is categorised as a Read tool in the KSeF MCP MCP Server, which means it retrieves data without modifying state.
Register the KSeF MCP server in PolicyLayer and add a rule for ksef_validate_invoice_draft: 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.
ksef_validate_invoice_draft is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ksef_validate_invoice_draft 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.
Set action: deny in the PolicyLayer policy for ksef_validate_invoice_draft. 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.
ksef_validate_invoice_draft 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →