Firmen aus Daylite auflisten (REST API)
AI agents call daylite_list_companies to retrieve information from Daylite Claude Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of companies from the CRM system. It has no side effects, does not modify data, and performs a simple read operation typical of CRM data retrieval. The low severity reflects the minimal risk from exposing company information retrieval, though the specific sensitivity depends on data classification policies.
From the tool's definition Tool name contains 'list' and description states 'auflisten' (German for 'list'), indicating data retrieval. The REST API call retrieves companies from Daylite CRM without modification.
Attacks that exploit this kind of access
Firmen aus Daylite auflisten (REST API). It is categorised as a Read tool in the Daylite Claude Connector MCP Server, which means it retrieves data without modifying state.
Register the Daylite Claude Connector MCP server in PolicyLayer and add a rule for daylite_list_companies: 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.
daylite_list_companies 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 daylite_list_companies 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 daylite_list_companies. 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.
daylite_list_companies 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.
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 →