AI agents call export_transactions_csv to retrieve information from Sevdesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads/retrieves bank transaction data and exports it as a CSV file. It queries existing data without modifying, deleting, or creating anything. The export is a read operation with no side effects.
From the tool's definition Export bank transactions as CSV from sevdesk
Attacks that exploit this kind of access
Export bank transactions as CSV from sevdesk. It is categorised as a Read tool in the Sevdesk MCP Server, which means it retrieves data without modifying state.
Register the Sevdesk MCP server in PolicyLayer and add a rule for export_transactions_csv: 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 Sevdesk. Nothing to install.
export_transactions_csv 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 export_transactions_csv 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 export_transactions_csv. 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.
export_transactions_csv is provided by the Sevdesk MCP server (codestra/sevdesk-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 →