get_sandbox_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-sandbox-diff.md

WHAT IT DOES

What get_sandbox_diff does on Sanka MCP Server

AI agents call get_sandbox_diff 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 get_sandbox_diff is rated Low

This is a read-only tool that queries and compares configuration data between sandbox and production environments. It retrieves information to help operators understand differences before making changes elsewhere. No data is modified, deleted, executed, or financial impact occurs. The blast radius of misuse is minimal—an AI could only retrieve diff information that an authorized user already has access to.

From the tool's definition The tool 'get_sandbox_diff' performs comparison and returns counts and lists of configuration differences.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_sandbox_diff 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 get_sandbox_diff, this is the rule to start with:

get_sandbox_diff Allowed

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

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 get_sandbox_diff call is checked against it from then on.

FAQ

Questions about get_sandbox_diff

What does the get_sandbox_diff tool do? +

Compare the sandbox configuration against production per family (views, workflows, fields, pipelines, …): counts and bounded item lists for new-in-sandbox, modified-since-copy, and production-only. Use this as the checklist before re-applying tested changes to production. 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_sandbox_diff? +

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

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

Can I rate-limit get_sandbox_diff? +

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

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

get_sandbox_diff 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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