AI agents use add_tag_to_object 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.
Adding tags is a write operation that modifies object metadata reversibly. It does not read sensitive data in aggregate, does not execute arbitrary code, does not delete data, and does not involve financial transactions. The blast radius is minimal—misuse would only affect organizational tagging/categorization of business objects, not core data integrity or financial state.
From the tool's definition Tool name 'add_tag_to_object' and description 'Add a tag to an object (contact, invoice, etc.)' indicates creating or modifying metadata tags on existing business objects. This is a reversible operation (tags can be removed).
Attacks that exploit this kind of access
Add a tag to an object (contact, invoice, etc.). 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 add_tag_to_object: 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.
add_tag_to_object 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 add_tag_to_object 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 add_tag_to_object. 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.
add_tag_to_object 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 →