New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_pipeline_snapshot_batch

Load one pipeline snapshot batch and its captured deal rows. Use this to inspect the frozen deal values behind a snapshot diff.

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/get-pipeline-snapshot-batch.md

What get_pipeline_snapshot_batch does on Sanka MCP Server

AI agents call get_pipeline_snapshot_batch 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.

Why get_pipeline_snapshot_batch is rated Low

This tool retrieves historical snapshot data for inspection purposes only. It queries existing frozen deal values without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal as it only exposes read access to snapshot data, classified as a Read operation with low severity.

From the tool's definition Tool description states 'Load one pipeline snapshot batch and its captured deal rows' and 'inspect the frozen deal values' — purely retrieval operations with no modification, deletion, or side effects.

Questions about get_pipeline_snapshot_batch

What does the get_pipeline_snapshot_batch tool do? +

Load one pipeline snapshot batch and its captured deal rows. Use this to inspect the frozen deal values behind a snapshot diff. 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 get_pipeline_snapshot_batch? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_pipeline_snapshot_batch: 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 get_pipeline_snapshot_batch? +

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

Can I rate-limit get_pipeline_snapshot_batch? +

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

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

get_pipeline_snapshot_batch 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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sanka MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.