AI agents call get-pipeline to retrieve information from Pipedrive MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a specific pipeline from Pipedrive CRM by its ID. The 'Get' verb and absence of any modification, deletion, or external side effects clearly indicate a Read category classification. The severity is low because retrieving pipeline configuration data poses minimal risk even if accessed by an unauthorized agent—it does not alter state, delete data, or trigger external operations.
From the tool's definition Tool name 'get-pipeline' and description 'Get a specific pipeline by ID' indicates a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get-pipeline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pipedrive MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-pipeline:
{
"version": "1",
"default": "deny",
"tools": {
"get-pipeline": {}
}
}get-pipeline is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific pipeline by ID. It is categorised as a Read tool in the Pipedrive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for get-pipeline: 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 Pipedrive MCP Server. Nothing to install.
get-pipeline 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 get-pipeline 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 get-pipeline. 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.
get-pipeline is provided by the Pipedrive MCP Server MCP server (teapot-agency/mcp_pipedrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pipedrive MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Pipedrive MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.