snow_get_customer_history

Retrieve complete customer interaction history

SERVERSerac SOURCEserac-labs/serac

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/serac/snow-get-customer-history.md

WHAT IT DOES

What snow_get_customer_history does on Serac

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

RISK

Why snow_get_customer_history is rated Low

This tool queries and retrieves customer data without modifying, executing, or deleting anything. However, the sensitivity is elevated to 'medium' rather than 'low' because customer interaction history likely contains PII (personally identifiable information), sensitive business data, or confidential communications.

From the tool's definition Tool name 'snow_get_customer_history' and description 'Retrieve complete customer interaction history' indicate a data retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snow_get_customer_history safely

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

snow_get_customer_history Allowed

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

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

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

FAQ

Questions about snow_get_customer_history

What does the snow_get_customer_history tool do? +

Retrieve complete customer interaction history. It is categorised as a Read tool in the Serac MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on snow_get_customer_history? +

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

What risk level is snow_get_customer_history? +

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

Can I rate-limit snow_get_customer_history? +

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

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

snow_get_customer_history is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Serac, and thousands of servers like it.

This server

All 432 Serac tools →

Across the catalogue

aiva_get_customer on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team 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 →