AI agents use create_contact 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.
This tool creates a new contact record, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. However, severity is elevated to 'medium' rather than 'low' because creating contacts in a financial/accounting system can have downstream effects on invoicing, orders, and transactions; an agent creating fraudulent or incorrect contact records could cause operational…
From the tool's definition Tool name 'create_contact' and description 'Create a new contact (customer/supplier/partner) in sevdesk' explicitly indicate creation of a new data record in the accounting system.
Attacks that exploit this kind of access
Create a new contact (customer/supplier/partner) 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.
Register the Sevdesk MCP server in PolicyLayer and add a rule for create_contact: 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.
create_contact is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_contact 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 create_contact. 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.
create_contact 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 →