daylite_update_company · Daylite Claude Connector MCP

WHAT IT DOES

What daylite_update_company does on Daylite Claude Connector

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

WHY IT NEEDS A POLICY

Why daylite_update_company needs a policy

This tool modifies existing company data in the Daylite CRM system. It falls under Write category because it creates or modifies data reversibly—the change can be undone by updating again or reverting to a previous state. It is not Destructive (no permanent deletion), not Execute (no arbitrary code/command execution), not Financial (no money movement).

From the tool's definition daylite_update_company updates an existing company record in Daylite CRM. The German description 'Bestehende Firma in Daylite aktualisieren' translates to 'Update existing company in Daylite.' This is a modification operation that changes data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

daylite_update_company Rate-limited

daylite_update_company 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": {
    "daylite_update_company": {
      "limits": [
        {
          "counter": "daylite_update_company_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 Daylite Claude Connector, so you can run agents against it safely.

FAQ

Questions about daylite_update_company

What does the daylite_update_company tool do? +

Bestehende Firma in Daylite aktualisieren. It is categorised as a Write tool in the Daylite Claude Connector MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on daylite_update_company? +

Register the Daylite Claude Connector MCP server in PolicyLayer and add a rule for daylite_update_company: 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 Daylite Claude Connector. Nothing to install.

What risk level is daylite_update_company? +

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

Can I rate-limit daylite_update_company? +

Yes. Add a rate_limit block to the daylite_update_company 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 daylite_update_company completely? +

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

daylite_update_company is provided by the Daylite Claude Connector MCP server (wimwoeber/daylite-claude-connector). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.