AI agents call ksef_check_attachment_permission 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.
This tool queries the KSeF context to determine if FA(3) attachments are permitted for invoice issuance. It is purely informational—it retrieves or validates a permission state without modifying data, executing code, or triggering external operations.
From the tool's definition Tool name includes 'check' and description states 'Check whether' — a query operation that retrieves permission status. The verb 'may issue' describes the permission being queried, not an action the tool performs.
Attacks that exploit this kind of access
Check whether the current KSeF context may issue invoices with FA(3) attachments. 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_check_attachment_permission: 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_check_attachment_permission 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_check_attachment_permission 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_check_attachment_permission. 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_check_attachment_permission 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 →