amocrm_get_pipeline
A read tool on the All MCP server.
This record as markdown: /tools/allmcp/amocrm-get-pipeline.md
What amocrm_get_pipeline does on Allmcp
AI agents call amocrm_get_pipeline to retrieve information from Allmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why amocrm_get_pipeline is rated Low
The 'get' prefix is a standard convention for read-only operations that retrieve data. No creation, modification, deletion, code execution, or financial impact is implied by the tool name. The empty description prevents higher confidence, but the clear naming pattern leaves little doubt this is a retrieval operation.
From the tool's definition Tool name 'amocrm_get_pipeline' uses the 'get' verb, which indicates retrieval of data without modification.
Attacks that exploit this kind of access
The rule that runs amocrm_get_pipeline safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For amocrm_get_pipeline, this is the rule to start with:
amocrm_get_pipeline is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every amocrm_get_pipeline call is checked against it from then on.
Questions about amocrm_get_pipeline
amocrm_get_pipeline is a read tool on the All MCP server. It is categorised as a Read tool in the Allmcp MCP Server, which means it retrieves data without modifying state.
Register the All MCP server in PolicyLayer and add a rule for amocrm_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 Allmcp. Nothing to install.
amocrm_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 amocrm_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 amocrm_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.
amocrm_get_pipeline is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on All, and thousands of servers like it.
This server
Across the catalogue