Verfügbare Pipelines aus Daylite auflisten
AI agents call daylite_list_pipelines 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 retrieves or queries pipeline data from the Daylite CRM system. The verb 'list' and context of fetching available pipelines establish it as a Read operation. There is no creation, modification, deletion, or execution of external code. Severity is low because querying CRM metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'daylite_list_pipelines' and description 'Verfügbare Pipelines aus Daylite auflisten' (List available pipelines from Daylite) indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Verfügbare Pipelines aus Daylite auflisten. 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_pipelines: 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_pipelines 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_pipelines 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_pipelines. 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_pipelines 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 →