AI agents call list_check_accounts 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 queries and returns a list of existing bank account data without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius if misused by an AI agent; the worst outcome would be information disclosure of account metadata that is typically already visible to users with read access.
From the tool's definition Tool name is 'list_check_accounts' and description states 'List bank accounts from sevdesk' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List bank accounts 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 list_check_accounts: 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.
list_check_accounts 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 list_check_accounts 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 list_check_accounts. 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.
list_check_accounts 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 →