compare_pipeline_snapshots

Compare two pipeline snapshot batches and return amount, weighted amount, stage transition, close-date, and per-deal deltas. Omit batch ids to compare the latest two matching batches.

SERVERSanka MCP Server SOURCEsankahq/sanka-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/sankahq-sanka-mcp/compare-pipeline-snapshots.md

WHAT IT DOES

What compare_pipeline_snapshots does on Sanka MCP Server

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

RISK

Why compare_pipeline_snapshots is rated Low

The tool compares two existing snapshots and returns delta/analytical data. It only reads and computes differences between pipeline snapshots without modifying any data. No side effects are implied.

From the tool's definition Compare two pipeline snapshot batches and return amount, weighted amount, stage transition, close-date, and per-deal deltas

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compare_pipeline_snapshots safely

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

compare_pipeline_snapshots Allowed

compare_pipeline_snapshots 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": {
    "compare_pipeline_snapshots": {}
  }
}

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

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

FAQ

Questions about compare_pipeline_snapshots

What does the compare_pipeline_snapshots tool do? +

Compare two pipeline snapshot batches and return amount, weighted amount, stage transition, close-date, and per-deal deltas. Omit batch ids to compare the latest two matching batches. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on compare_pipeline_snapshots? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for compare_pipeline_snapshots: 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 Sanka MCP Server. Nothing to install.

What risk level is compare_pipeline_snapshots? +

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

Can I rate-limit compare_pipeline_snapshots? +

Yes. Add a rate_limit block to the compare_pipeline_snapshots 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 compare_pipeline_snapshots completely? +

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

compare_pipeline_snapshots is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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