get_revenue_pipelines

SERVERAdrata SOURCE@adrata/adrata-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/get-revenue-pipelines.md

WHAT IT DOES

What get_revenue_pipelines does on Adrata

AI agents call get_revenue_pipelines to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_revenue_pipelines is rated Low

Even though get_revenue_pipelines only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_revenue_pipelines safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_revenue_pipelines, this is the rule to start with:

get_revenue_pipelines Allowed

get_revenue_pipelines is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_revenue_pipelines": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every get_revenue_pipelines call is checked against it from then on.

FAQ

Questions about get_revenue_pipelines

What does the get_revenue_pipelines tool do? +

List actual revenue pipelines and evidence-backed suggested or decided stage moves. Moves respect the caller\u2019s visible deal owners. customer_success reads the customer pipeline, member choices and visible assignments; pass its nextCursor as after for the next page. This is the pipeline product, not saved pipeline views. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_revenue_pipelines? +

Register the Adrata MCP server in PolicyLayer and add a rule for get_revenue_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 Adrata. Nothing to install.

What risk level is get_revenue_pipelines? +

get_revenue_pipelines is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_revenue_pipelines? +

Yes. Add a rate_limit block to the get_revenue_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.

How do I block get_revenue_pipelines completely? +

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

What MCP server provides get_revenue_pipelines? +

get_revenue_pipelines is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 395 Adrata tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →