get_aggregate_data

THE RISK

Low Risk

Why get_aggregate_data needs a policy

This tool reads and computes statistical summaries from data in a table. It only retrieves/aggregates existing data without modifying, creating, or deleting anything. Aggregation operations like COUNT, AVG, SUM are purely read operations with no side effects.

From the tool's definition Performs an aggregation (COUNT, AVG, SUM, etc.) on a table, with optional grouping

Documented attack patterns abuse exactly the kind of access get_aggregate_data gives an agent:

POLICY

How to control get_aggregate_data

PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for get_aggregate_data:

policy.json

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

get_aggregate_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Snow — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Snow tools

Destructive delete_script_include Delete a Script Include from ServiceNow. Destructive delete_story_dependency Deletes an existing dependency relationship between user stories. Destructive delete_workflow Delete a workflow definition from ServiceNow. Destructive remove_group_members Remove multiple users from a group. Execute publish_changeset Publish a completed changeset so it can be retrieved from the remote instance. Write add_change_task Adds a new task to an existing change request. Write add_comment_to_incident Adds a customer-visible comment (updates the 'comments' field) to an existing incident. Write add_comment_to_request Adds a customer-visible comment to a request ticket (REQ).

All 88 Snow tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_aggregate_data

What does the get_aggregate_data tool do? +

Performs an aggregation (COUNT, AVG, SUM, etc.) on a table, with optional grouping. It is categorised as a Read tool in the Snow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_aggregate_data? +

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

What risk level is get_aggregate_data? +

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

Can I rate-limit get_aggregate_data? +

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

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

get_aggregate_data is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Snow tool call.

Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →