update_check_account · Sevdesk MCP: Risk & Policy

WHAT IT DOES

What update_check_account does on Sevdesk

AI agents use update_check_account to create or update resources in Sevdesk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sevdesk environment.

WHY IT NEEDS A POLICY

Why update_check_account needs a policy

The tool creates or modifies data (a bank account record) in a reversible manner. While it touches financial infrastructure, it does not move money or create financial obligations itself—it updates account metadata/configuration. This is categorized as Write rather than Financial because the action modifies the account record itself rather than executing a payment or transaction.

From the tool's definition Tool name 'update_check_account' and description 'Update an existing bank account in sevdesk' indicate modification of bank account data. This is a reversible write operation that modifies financial records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_check_account Rate-limited

update_check_account stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_check_account": {
      "limits": [
        {
          "counter": "update_check_account_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sevdesk, so you can run agents against it safely.

FAQ

Questions about update_check_account

What does the update_check_account tool do? +

Update an existing bank account in sevdesk. It is categorised as a Write tool in the Sevdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_check_account? +

Register the Sevdesk MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_check_account? +

update_check_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_check_account? +

Yes. Add a rate_limit block to the update_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.

How do I block update_check_account completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_check_account? +

update_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.