AI agents call get_check_account 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 retrieves banking account information by ID. It performs a read-only query against the sevdesk API with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal — exposing bank account details is a data leak risk but does not enable financial transactions, account manipulation, or destructive actions. Classified as Read/low severity.
From the tool's definition Tool name is 'get_check_account' and description states 'Get a specific bank account by ID from sevdesk' — uses the verb 'Get' which indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get a specific bank account by ID 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 get_check_account: 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.
get_check_account 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 get_check_account 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 get_check_account. 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.
get_check_account 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 →